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

Re: Directory locking: current goals

From: Brian W. Fitzpatrick <fitz_at_collab.net>
Date: 2004-10-15 22:08:10 CEST

On Oct 15, 2004, at 2:54 PM, Philip Martin wrote:

> Mark Benedetto King <mbk@lowlatency.com> writes:
>> On Fri, Oct 15, 2004 at 08:06:20PM +0100, Philip Martin wrote:
>>> I assume "collection membership" means adding and removing elements,
>>> but not modifying existing elements. That's more or less the way
>>> Clearcase works so it's likely to be feasible. The main difference
>>> is
>>> that Clearcase requires the directory to be committed for
>>> adds/deletes
>>> to take effect while Subversion allows the elements to be committed.
>> I think Subversion does logically commit the directory when the
>> element is committed; that's what the bubble-up is.
> You cut my example :-(
> $ svn lock dir
> $ svn add dir/foo
> $ svn rm dir/bar
> $ svn ci dir/foo
> Clearcase requires the equivalent of "svn ci dir" so both the add and
> the rm get committed; Subversion allows just one to be committed.
> What happens to the lock and the uncommitted modification?

I would think the lock would remain, and the uncommitted modification
would have to be committed at a later point.

Is the issue that you are pointing out here "at what point is the
directory lock released?" If so, I would imagine it would be released
only when you either a) unlocked it explicitly, or b) committed the
directory itself.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 15 22:08:51 2004

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

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