On Oct 24, 2004, at 9:34 PM, HAND,Nathan wrote:
> Ok, I think I see your point. You're saying http://.../tags/1.0 isn't a
> tag because somebody can commit a change to that URL. That makes sense.
>
> Would it be sufficient to specify a tag as both a revision and a URL?
> That tag is immutable because every subsequent change results in a new
> revision. So...
>
> svn -r 12345 checkout http://.../tags/my-tag
>
> The tuple (12345,http://.../tags/my-tag) should be immutable. Or have I
> misunderstood the problem?
That is part of it. The other part is seeing where a particular
project has been tagged. I log of any project should show which
revisions were tagged and what those tags are.. otherwise the tag
isn't nearly as effective. How in subversion do you find out which
revisions of a project were tagged and how to get those revisions? See
how a copy is conceptually not a tag? It is too disconnected from the
original. Think of the Visual Source Safe concept - where the term
used is "label". To see the labels you look at the thing you labeled
and you can see which versions were labeled and what the labels were.
As far as I know (and I'm new to subversion, so I could be out to
lunch), with subversion, you must look at tags in a context not
associated with what they are tagging and work backwards to try to see
what they tagged.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 25 04:02:46 2004