Robert Graf-Waczenski wrote:
> For this, a very simple concept of a label would suffice:
> A text that can be associated with a revision number.
> This text must be *independent* of the commit message that was
> supplied by the committer of the change that created the
> given revision number. It is as simple as sticking a post-it
> to the correct sheet in a huge pile of paper. (Thanks to the
> other poster who used this analogy!)
Well, glad I could help... :) I meant it as a negative point, not a
positive point, but oh well.
Now imagine a repository of about 20,000 revisions (give or take a few).
Do you still like to search through the entire pile? I'd prefer a
separately stored copy.
And now think about your tag being a collection of several pages from
different document versions, would you still like to search for all
those post-it notes which could be on any page of any version of any
document in the pile.
> And, to stay with this
> analogy, removing the post-it and sticking it on a different
> paper or writing a different text on it should also be possible.
Keep in mind the danger that it's not possible to look back anymore for
this change. Which, in the case of many users, could lead to trouble.
> I don't want to have to look through all the /tags
> subfolders, then lookup the file, then open this file's
> history to determine if the offending change is there or not.
I bet your /tags directory is smaller than your /trunk and that it has
lesser revisions...
Danny
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 21 18:30:23 2006