Windows file locking with bzr 2.2.3

[W. Trevor King]

On Thu, Feb 24, 2011 at 04:12:59PM -0600, John Arbash Meinel wrote:
> > I don't really understand how stricter locking ties into explicitly
> > listing a root directory, but I suppose that doesn't really matter to
> > me ;).
> 
> We use a read lock while reading the list of files, to ensure that
> things don't change in the middle. (Otherwise you might see a file, but
> not the containing directory, for example.)
> 
> We use a write lock while updating the tree, to ensure that the data
> structure stays consistent. (Otherwise process 1 might try to add foo,
> and process 2 might add bar, and one of them would ignore the others
> changes, etc.)

But why both of them for cmd_add with an explicitly given file list?
Wouldn't you just need a write lock?

-- 
This email may be signed or encrypted with GPG (http://www.gnupg.org).
The GPG signature (if present) will be attached as 'signature.asc'.
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110224/ab7f1ac9/attachment.pgp>