Re: [Locking] commit and unlock

Ben Collins-Sussman wrote:
[snip]
>
> 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.

> My feeling is: 'svn commit' should only change the things it
> committed. That's how it works now, and it seems pretty simple and
> clear. If 'svn commit' started removing locks just because they're
> "nearby" things that were committed, we'd be violating the rule.

+1.

-John

---------------------------------------------------------------------
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:23:18 2004