Windows file locking with bzr 2.2.3

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-02-24 05:03 PM, W. Trevor King wrote:
> On Thu, Feb 24, 2011 at 03:47:52PM -0600, John Arbash Meinel wrote:
>> On Windows, taking an exclusive lock blocks all other requests, even
>> from the same process. IMO Windows makes more sense here, for whatever
>> the purpose of locking the file, most logic will assume they got what
>> they asked for. (Thread1 thinks it has an exclusive lock, so does
>> thread2, but they can both mutate the state on Linux.)
> 
> 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 ;).

I'm not sure what you mean by "explicitly listing a root directory."
That's not what "--file-ids-from" does, if that's what you're thinking.

> I hope nobody ever emails the BE list requesting file locking, since
> it looks really annoying ;).

One thing missing from your test script is bzrlib.initialize(), which is
recommended with bzr 2.2 and later.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1m2OcACgkQ0F+nu1YWqI05WQCfX4nIaySEW39ywyHJVPW1eBPD
PygAniyog1p5SpK6gEhFaBqyutxN44vk
=/L4Z
-----END PGP SIGNATURE-----