[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn vs cvs and version numbers

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-07-04 19:20:26 CEST

Clemens wrote:
>> * In CVS, we can check out version 1 of foo.php and version 2 of bar.php
>> into a sandbox, tag it as RELEASE_TWO and move RELEASE_TWO into production.
> No problem in SVN as well. You may compose your working copy by manually
> selecting different revisions for any single file and/or dir within by
> using the 'switch' subcommand of 'svn'.
> Then you simply 'tag' this composition as RELEASE_TWO if you like to
> preserve your work for eternity. :-)
> The only "problem" that may occure is, that you cannot really 'move'
> your 'tags' *after* application, as there are no 'tags' at all in SVN ;-)

Tags aren't attributes of the files as they are in svn, but you can
still use named directories as tags to hold groups of specific revisions
  together. If your work flow depends on having a specific name for a
tag for an operation, you can emulate moving a tag by deleting the
previous one, then copying a new workspace to that name. The
delete/copy operations can't be done atomically, so whatever uses the
tag must be coordinated with the updates but since cvs did not do
anything atomically you had to do that anyway. Since you need this
coordination anyway you might find it easier to just use a new name for
each tag.

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 4 19:20:28 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.