On Oct 22, 2004, at 1:41 PM, John Szakmeister wrote:
> David F. Newman wrote:
>> On Fri, 2004-10-22 at 06:10, pushok wrote:
>>
>>> With your approach there NO difference between TAG and BRANCH. All
>>> that is the COPY. One copy, called TAG we _promise_ do not change.
>>> And
>>> that's why it is a TAG. But nothing can prevent me from modifying
>>> this
>>> COPY. So, some "bad" developer CAN change the TAG.
>>
>> One can force a read-only policy on tags by making the /tags directory
>> read-only to everyone except the release coordinator using
>> mod_authz_svn. Then a bad developer can't change tags.
>
> This can also be forced by using a pre-commit hook script. I made one
> that allows you to create a tag, but you can't commit any changes
> under it.
In other words, you had to write your own code to work around the lack
of this feature in subversion. :)
I would think that subversion could support some sort of standard
property that indicated "this copy is a tag" and then it could enforce
the immutability of that copy in some way.
For ease of use the svn copy command could have a flag to say I'm
making a "tag" copy, and the "tag" property would automatically be set
on the copy.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 22 19:58:16 2004