Re: Branch philosophy

Duncan Murdoch murdoch-at-stats.uwo.ca |Lists| wrote:
> If it's a stable branch containing patches for a release, then this
> wouldn't make sense. Even if you have no plans to continue patches
> for that release, someone might, someday in the future.

This is almost a FAQ isn't it? "How do I make a branch/tag read-only".
(It isn't in the FAQ.) Well you can't unless you fiddle with apache
configuration. (I'm using svn+ssh so I'm out of luck anyway).

I have no idea how difficult it would be to implement, but form a users
point of view it would make sense to be able to

svn propset -m "Locking the branch" svn:nocommit $url

or something equivalent and have that affect the entire subtree below
it, preventing commits to it.

But today we can't. (Something for a pre-commit hook? I've never written
one..)

-------------

Actually, I just noticed that subversion doesn't store the read-only
"bit" for directories or files either.. Hmm. My mistake? Regardless,
that (preventing writing in the checked-out working copy) would not be
the same as the the svn:nocommit property I suggest above (disabling
commits).

Peter

-- 
Peter Valdemar Mørch
http://www.morch.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org