[PATCH 1 of 1 STABLE] readlock: close lock file as early as possible

Matt Mackall mpm at selenic.com
Sat Dec 4 17:04:31 CST 2010


On Fri, 2010-12-03 at 01:33 +0100, Adrian Buehlmann wrote:
> # HG changeset patch
> # User Adrian Buehlmann <adrian at cadifra.com>
> # Date 1291335788 -3600
> # Branch stable
> # Node ID a8d607c0565008848e207a54dc08ca3edff005fe
> # Parent  5e51254ad4d4c80669f462e310b2677f2b3c54a7
> readlock: close lock file as early as possible
> 
> Avoiding Windows' "scheduled delete" state on the lock file, which
> happens if the lock file is unlinked while it is open.
> 
> Scheduled delete state prevents creating the lock file, which
> is bad.

What happens? Don't we simply try again in a loop?

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list