On Tue, 14 Dec 2004, Ben Collins-Sussman wrote:
>
> On Dec 14, 2004, at 12:11 PM, Peter N. Lundblad wrote:
> >
> > IN any case there is the question if only the committables (the files
> > that
> > were actually changed) or all files specified by the targets (and
> > possibly
> > recursively) should be unlocked. I think the latter is the best. If you
> > commit a subtree with some locked files, a lock shouldn't be left just
> > becvause the file wasn't modified.
>
> 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
This is a good point. OHO, you have the same problem if you actually
started work on baz.jpg before comitting foo/bar. But then you would see
it when editing the log message, so I guess I am convinced.
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 14 20:15:42 2004