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

Re: CVS and SVN: Tags and Branches.. A question of strategies

From: Jeff Smith <jsmith_at_robotronics.com>
Date: 2007-03-15 19:48:04 CET

On Thursday 08 March 2007 10:45, Les Mikesell wrote:
> > I can tell that deep down you know the two are much the same:
> > * A [tag]    is a tree of files given a name, and selected from
> > certain revisions of certain files.
> > * A [branch] is a tree of files given a name, and selected from
> > certain revisions of certain files.
> >
> > Then why does cvs track them two different ways? Why to make it
> > more complicated, of course ;-)
> No, in cvs, a tag is just a label applied to a file/revision to
> make it easy to find a set with that label again and do group
> operations on them.  Tags never divorce a file from its subsequent
> revisions as can happen in subversion.

Les, I think you misunderstood me. I agree with you, and what I said
*is* correct (except that I could not think of a good way to word
it). I atempted to describe the result of "what we do" with tags and
branches. You are thinking in terms of "why we do it" and cvs
internal workings, but I am saying to forget that for now. Anyway, in
that statement I was only explaining why `svn copy` is ideal for
tagging. When you say "No" as if I was wrong, either you
misunderstand or you are saying that Subversion has no 'tagging'
capability just because it only uses 'copy'.

I do hope you could clarify what you mean though, that subversion
could "divorce a file from it's subsequent revisions". Did you mean
somehow it could lose the history, in what situation?

I realize it's probably not the question of this thread. I've learned
I just can't understand anything without making sure I understand
it's precepts.

> I think the unanswered question is, starting from a subversion tag
> copy, where subsequent work has been done on the corresponding files
> in branch/trunk copies, how do you take only the tagged files, but
> advance them to HEAD (or some arbitrary rev number)? In cvs, since
> all revisions exist in a single versioned file, you can look
> 'forward' past the tag. What is the equivalent subversion
> operation, especially for tags copied from a working copy where the
> tagged revision may not match anything else in the repository?

Although I still don't see any problem with doing all this in
subversion, I just don't see any example to use. Could someone spell
out the problem in steps, and maybe how it is done in cvs?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 15 19:48:49 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.