Re: Controlling project version

From: Date: Mon, 18 Jun 2007 06:39:05 +0000
Subject: Re: Controlling project version
References: 1 2 3  Groups: php.general 
Request: Send a blank email to php-general+get-257258@lists.php.net to get a copy of this message
I fail to see the difference between "just a script" and "a proper program", but regardless...
I think of a "script" as something like a firewall script - where-as cvs/subversion have a bunch of different commands to do different things. All interpretation I guess :P
I use cvs at work (because it was more mature at the time I set it up) and subversion at home.
CVS wraps RCS, so you have used it!
OK I haven't used RCS *directly* - Happy? ;)
I don't like the branching in subversion, it's a lot easier to work with in CVS.
That's odd since this is one of the major advantages that Subversion has over CVS (for me at any rate). When you branch or tag in CVS it will sit there and create a copy of every single file in the repository. Depending on the size of your projects this can take a while.
Maybe it's just the whole structure thing I don't understand: http://svnbook.red-bean.com/nightly/en/svn.tour.importing.html#svn.tour.importing.layout If you already have your project in subversion, how do you branch it? Compare that to: cvs tag -b "branch name" module_name ;) -- Postgresql & php tutorials http://www.designmagick.com/

« previous php.general (#257258) next »