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

Re: version control of labels

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-06-06 10:19:12 CEST

On Wed, Jun 06, 2001 at 12:37:33PM +0530, Harindranath P. R wrote:
>...
> I am not sure this fixes the problem that AccuRev claims to fix. The claim
> they make is that since tags are also versioned it is possible to retrieve
> the exact version corresponding to a tag as it was even if later that tag is
> redefined. How does the clone address this? Is redefining a clone not
> allowed?

The copy is a specific revision in the repository. If you want to further
modify that copy, the you'll be making addition revisions.

As a concrete example:

  Let's say that we want to "tag" the HEAD. In SVN, we do:
  
  $ svn cp /trunk /tags/0.9.3-alpha
  $ svn commit
  
  Developers continue to make changes on /trunk. Let's say that a few days
  later, we want to include a modified file into 0.9.3-alpha:
  
  $ svn cp /trunk/some/file /tags/0.9.3-alpha/some/file
  $ svn commit

In the above scenario, the two commits each create a new revision. You can
retrieve the state of the initial "cp", and you can retrieve the modifed
0.9.3-alpha.

If somebody (two months later) does a "cp" over the top of 0.9.3-alpha, then
we'll *still* be able to back up a revision and grab the original.

The underlying capability here is that we version directories. A particular
revision of a directory encapsulates all of its members *and* their
revisions at that point in time. Future changes fall into a different
directory revision.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:31 2006

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