I vaguely recall reading in the mailing list archives about this. From
what I recall, there is no support for making a branch/tag read-only.
The thread was in the context of creating a new feature that would allow
you to "tag" files in a read-only manner. I forgot what the person had
called it.
I think you are on to an interesting approach with a hook script. So
that you wouldn't have to modify the script for each new branch/tag,
couldn't you just identify a set of operations that are allowed on say
tags/, that only permit the "creation" of files, but not modification?
--joe
Ron Olson wrote:
> Hi all-
>
> I've been going through the Subversion book (printed the whole thing
> out) but haven't found anything that really answers this question: Can
> I lock a branch/tag so that no changes can be made to it? I am using
> this particular repository for documents that become a printed
> catalog; once the docs are at the printer, they should never, ever be
> changed again; I need to make sure that I can always print out this
> branch and have exactly what was sent to the publisher.
>
> I can't rely on anybody reading my comments ("DO NOT CHANGE!"), I can
> lock the documents but others can steal the locks, and I was thinking
> of writing a hook script to prevent a commit to the branch taking
> place, but it seems ...silly to have to modify it for each new branch.
>
> Is there any good, standard ways of doing this?
>
> Thanks,
>
> Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 7 00:20:11 2006