[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Locking to prevent changes to a branch?

From: John Browne <jkbrowne_at_gmail.com>
Date: 2005-06-23 04:19:07 CEST

Right, I did get that far on the logic. But, what happens if, say a
developer checks out "/sharedproject/tags/release001", doesn't modify
any existing files, but *does* add a new, previously unversioned file.

The commit will succeed using the above logic, will it not? :)

On 6/22/05, Ben Collins-Sussman <sussman@collab.net> wrote:
> On Jun 22, 2005, at 9:06 PM, John Browne wrote:
> > I am also trying to accomplish this with my existing hook script. I
> > would like users to be able to *create* new tags, but never modify
> > them. I'm not 100% sure of the correct logic, though. I would like
> > to understand what needs to happen in the hook script regarding the
> > path/revision/transaction checking, etc. Many people have directed me
> > to the existing perl or python access-control scripts that are bundled
> > with subversion, but I'm trying (on purpose) to do it the hard way.
> >
> > Anyone have any clues?
> >
> Sure, examined the changed paths in the impending commit
> transaction. If any of them affect /tags/*, disallow the whole
> commit. The exception, of course, is a changed-path that claims to
> be an "addition" of /tags/*. That's fine.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 04:20:49 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.