Archie Cobbs wrote:
> Paul Moore wrote:
>> I'm OK with Subversion's approach of using cheap copies as tags (I
>> am, honest I am, no really...) but one thing I do feel somewhat
>> nervous over is that a "tag" is neither more nor less "frozen" than
>> any other copy of the project. Mistakes, misunderstandings, or even
>> lazy "it won't matter" shortcuts do happen, and the integrity of a
>> tag can be lost.
>>
>> Ideally, I'd like to make the tags subdirectory of my repository
>> "create only" - ie, copies can be added to the tags directory, and
>> read, but once they have been created they cannot be updated.
>
> Are you sure you really want that? I've often been involved in projects
> where a tag needed to be move because of some last minute adjustment
> to a file, or because the tag was applied incorrectly.
So, the smart thing to do is to allow create and delete, but block
modification.
> If you want a "tag" that works today and represents an unchangable
> snapsnot, revision numbers work pretty well :-)
>
> Maybe you could just add unversioned properties to your repository like
> "local:MY_FAVORITE_TAG" -> "1432". These would be unchangeable in the
> sense that by default subversion is configured to disallow modifying
> unversioned properties (right?), so an admin action would be required.
Which includes disallowing *creating* them in the first place, by default.
Besides, this requires manual lookup of the revision to use the "tag", and
you need to memorize which branch the revision number is referring to.
Messy. Go with subversion's normal tags instead.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 1 01:48:24 2004