If I've followed everything in this thread properly, it looks like the
idea that was proposed of a user-defined revision number 'alias' akin
to HEAD, that is maintained on the server side so it can easily be
shared among clients, would deal with the issue that users are having
with the current tag system.
What I haven't seen clearly stated is a reason that such an alias is
better the current tag system with a pre-commit hook to prevent
modification of tags. (Personally I believe such a thing would be very
useful.) It has also been proposed that such a hook be included with
subversion rather than having all users deal with this on their own.
I for one think there is room for improvement on the current cheap-copy
tag system. Though I see that is it powerful as is. The example
brought up about not seeing where things were tagged when viewing a log
of the trunk is good. I think the alias idea would make it easier to
deal with specific tagging issues that seem to fit awkwardly into the
current system.
For example end users need to come up with fancy repository layouts to
make the 'tags' branch manageable. You can have tags of the trunk,
tags of branches, tags of branches of branches, etc.. and fitting all
those tags into another repository tree under 'tags' is not an easy
thing to keep organized. Having the 'label' stuck to the actual
branch that it is supposed to be 'tagging' seems to have some
advantages that the current system cannot handle well.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 27 15:38:52 2004