> What great problem are you solving here? Are your users constantly
> committing changes to tag-directories? (And if they do, so what?
> Slap them on the hand and revert the change.)
Nope they are not. At least not here. But you could ask yourself: do
we relly need a version control system at all. If everybody takes care
in naming directories and copying files we dont even need a version
control.... :-) Just kidding. But with svn:final I just want to be
sure my todays tag will have the same contents it has today. I dont
even want to have to check for it (revision numbers or such). If a
customer needs to have a specific tag i want to retrieve exactly that.
Today tomorrow and in twenty years, no matter what....
> This looks like a complex feature for little gain. We already have
> two different access control methods (pre-commit hooks and
> mod_authz_svn), and there's already been discussion for real ACLs in a
> post-1.0 repository someday.
While reading the messages (for example with mod_authz_svn) I got the
impression its rather hard to forbid committing to a specific url with
regexes. And of course one had to use pre-commit hooks since
mod_authz_svn doesnt care got the svn:,svn+ssh: and file: users. But
maybe I picked the wrong messages here while researching...
Xela
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 2 19:00:50 2003