On 6/28/06, email@example.com <firstname.lastname@example.org> wrote:
> The basic command is 'tag':
> $ svn tag version-1.0 -r 20120
> and then it is possible to issue commands like:
> $ svn update -r version-1.0
How do you search for the revprop? By brute force?
> I have searched the mailing list archives, and have found "tags"/"labels"
> to be a popular topic - this must be because many people believe
> Subversion is missing a simple tag feature.
Yes, and the general consensus of the subversion developer community
is that this a small (but vocal!) minority, and that they are wrong in
thinking that 'svn cp trunk tags/version-1.0' isn't a "true tag".
> By restricting the use of 'untag', perhaps even removing it, it will be
> difficult to remove tags. And it will be possible to see when and who last
> changed the tag (by the date and author information).
I really don't want to open this debate again. :-) Here's a quick summary.
The general feeling among subversion developers is that the 'label'
technique of tagging (the way CVS does it) is an inferior strategy for
tagging, because there's no accountability. In the model you propose
(as well as in CVS) there's no record of anyone creating a label, nor
is there any record of someone changing the label or deleting it. In
the subversion defnition of "tag" (a cheap directory copy), the act of
tagging is an historical event, recorded forever in the history. If
someone deletes or accidentally changes the tag, that's recorded as a
commit as well. A label/revpropsimply doesn't provide any of this
sort of tracking.
The main reason people seem to ask for labels-as-tags is because they
fear that directories-as-tags are too prone to accidental commits. If
you're really worried that this may happen (i.e. nobody will notice
the commit email), then just put access control on the tags/
directory. Write a pre-commit hook script which allows new tags to
appear, but rejects commits that alter them.
As an aside: it *would* be nice to see a server-side feature that
allows efficient searching of revprops. We tell people to invent
revprops, but they mostly useless when they're not easily searchable.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jun 29 02:49:11 2006