Marc Haisenko wrote:
> I really don't see any point in "tags" other than having names for certain
> revisions. Could someone please enlighten me why so many people keep on
> insisting that tags are important when the only use in such a feature in
> SubVersion would be to have an "alias" for a revision number ?
One problem of not having CVS-style tags is
that you don't -KNOW- "where, if, when" the tag has been put
on a file or folder.
you have to manually scan through thousands of
/Repos/tags/tag-XX-YY-ZZ folders and look if your
file is possibly there in some tags/ or branches/ dir
and even then you cant be sure if it is the same file -
just because it's equally named doesn't mean its the same.
lets assume someone has the files (or folders, doesnt matter)
now he puts a tag on file000.txt
svn cp (url)/trunk/file034.txt (url)/tags/tags/MyDevTag01/file034.txt
another tag, maybe even mistypes or changes the name...
svn cp (url)/trunk/file020.txt (url)/tags/tags/MyDevTag02/file200.txt
another tag, from another folder with the same name...
svn cp (url)/trunk/other/file020.txt (url)/tags/MyOtherTag02/file020.txt
or from some modified branch,
svn cp (url)/branch/Branch26/file020.txt
how do you ever find these "tags" within thousands of tags
(if you don't remember the precise url name and source
for each tag) by looking at the /trunk and /tags folders ?
its also complicated to find out where they originated from
or where they could be merged back (no direct link to their
I don't say the information isnt there, -somewhere-,
but its really hard to get it out.
the repos layout is freely configurable so NO tool can
assume a specific layout.
e.g. TSVN has to *guess* some things based on whether a
path contains the words "/tags/" or "/branches/".
everybody must write his own tools specific to his
own repository layout rules...
even if it would take a fortune O(x) for svn to calculate
responses on such questions, then that's still better than
to be unable to answer it at all.
see it the other way: everybody is using CVS tags,
even though it can be slow.
for example TortoiseCVS and other tools draw really nice
and helpful revision-graphs ( probably based on cvs status -v )
for cvs files where you can see when each file was branched,
tagged, modified or merged back.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Apr 2 17:33:43 2004