##// END OF EJS Templates
merge: don't grab wlock when merging in memory...
merge: don't grab wlock when merging in memory I noticed this because we have an internal extension that does an in-memory rebase while holding only a repo lock, which resulted in a developer warning about the working copy lock being taken after the repo lock. Differential Revision: https://phab.mercurial-scm.org/D8665
Martin von Zweigbergk -
r45536:d1471dbb default
Show More
Name Size Modified Last Commit Author
/ contrib / python-zstandard / zstd / common
bitstream.h Loading ...
compiler.h Loading ...
cpu.h Loading ...
debug.c Loading ...
debug.h Loading ...
entropy_common.c Loading ...
error_private.c Loading ...
error_private.h Loading ...
fse.h Loading ...
fse_decompress.c Loading ...
huf.h Loading ...
mem.h Loading ...
pool.c Loading ...
pool.h Loading ...
threading.c Loading ...
threading.h Loading ...
xxhash.c Loading ...
xxhash.h Loading ...
zstd_common.c Loading ...
zstd_errors.h Loading ...
zstd_internal.h Loading ...