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

Re: [Locking] commit and unlock

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2004-12-15 00:40:34 CET

John Szakmeister wrote:
> Ben Collins-Sussman wrote:
>>I disagree about this. People often have multiple changesets going
>>on in their working copies. For example, I may lock foo/bar/baz.jpg
>>because I plan to edit it as part of Changeset A. Then I might
>>switch gears and change a bunch of other files in foo/bar/, as part
>>of Changeset B. Then I run 'svn commit foo/bar/' to commit Changeset
>>B. I would be really annoyed if that released my lock on baz.jpg!
> I agree with you Ben. I often have several changes running through my
> working copy.

See my reply to Ben: how do you justify wanting any locks on unchanged sibling
files to be left alone while, already, any changes to sibling files get committed?

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 15 00:43:18 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.