[Commented On] D11817: sparse: lock the store when updating requirements config

[marmoute (Pierre-Yves David)]

marmoute added a comment.
marmoute accepted this revision.


  In D11817#181925 <https://phab.mercurial-scm.org/D11817#181925>, @aalekseyev wrote:
  
  > I tried this, and ran into another problem: dirstate is linked to wlock, so if you share a wlock then you must also share the dirstate.
  
  I see, the wlock's `releasefn` refer to the original dirstate.
  
  > I wrote a patch that does this, but I can't tell how safe that is. All tests pass, at least.
  
  That seems "fine", it test are happy, lets try this route.
  
  > @marmoute, please have a look at the patch.

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D11817/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D11817

To: aalekseyev, #hg-reviewers, Alphare, marmoute
Cc: marmoute, mercurial-patches
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-patches/attachments/20211216/e5818b1f/attachment-0002.html>