comparison tests/test-obsolete-bounds-checking.t @ 44999:d1471dbbdd63

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
author Martin von Zweigbergk <martinvonz@google.com>
date Wed, 24 Jun 2020 23:17:56 -0700
parents 44797aedfb35
children 7e5be4a7cda7
comparison
equal deleted inserted replaced
44998:f2de8f31cb59 44999:d1471dbbdd63