[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 06:01:20 CEST

Ahh.. Ok, I also just noticed "svnlook changed" lists both changed
files and directories. That was the other thing that had me stumped.
I thought I would have to do a "svnlook dirs-changed" to get the
directories seperately. Now I can put all the pieces together.

Thanks for the regex tips Ben. :)

On 6/22/05, Ben Collins-Sussman <sussman@collab.net> wrote:
> On Jun 22, 2005, at 9:19 PM, John Browne wrote:
> > 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? :)
> >
> You just need to keep your regular expressions really specific,
> looking for directory separators. In other words, an add of '/tags/
> blah' should be allowed, but an add of '/tags/blah/bloo' should be
> disallowed. Don't allow any directory separators after the initial /
> tags/ path.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 23 06:03:18 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.