Re: php + cvs
| From: | Jochem Maas | Date: | Tue, 31 May 2005 16:06:55 +0000 |
| Subject: | Re: php + cvs | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-216056@lists.php.net to get a copy of this message | ||
Bostjan Skufca @ domenca.com wrote:
Hello, is it possible to mount CVS/SVN repository as filesystem?a. why would you want to? (the whole idea is that you _dont_ edit files directly in the repository) b. this is a php mailinglist not a cvs mailinglist. ;-)
regards, Bostjan On Tuesday 31 May 2005 15:46, M. Sokolewicz wrote:Marcus Bointon wrote:On 31 May 2005, at 09:58, Jochem Maas wrote:another CVS/SVN helper-application is smartSVN (or smartCVS for CVS): http://www.smartsvn.com/ (http://www.smartcvs.com/ for CVS). Those applications are really nice, personally I find that they are far easier to handle than tortoiseCVS(/SVN)Also I hear lots of good things about subversion (SVN), which is a newer alternative for version control - some even say its better.I can definitely vouch for Subversion. I'm using it for all my PHP stuff. I'd not used cvs a great deal, but I'd always found it awkward and svn is certainly easier. The home page is here: http://subversion.tigris.org/ The documentation (an online O'Reilly book) is excellent. It's pretty easy to learn (shares most basic commands with cvs), and there are many helper apps to work with it, not least TortoiseSVN which looks and works just like TortoiseCVS. I'm on OSX with OpenBSD and Linux servers and it's been easy to get it working over HTTPS. There are some OSX clients (notably svnx), but I find that once you figure out the commands, the command line interface is very easy to work with. Consensus seems to be that if you're just starting out in version control, go straight to svn so you can skip all the reasons that made them want an upgrade from cvs! Marcus