Re: Locking to prevent changes to a branch?

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 04:35:50 2005