comparison mercurial/sparse.py @ 44150:ff22c76825b9

merge: don't call update hook when using in-memory context I'm pretty sure many hook implementors will assume that they can inspect the working copy and/or dirstate parents when the hook is called, so I don't think we should call the hook when using an in-memory context. The new behavior matches that of the preupdate hook. Differential Revision: https://phab.mercurial-scm.org/D7898
author Martin von Zweigbergk <martinvonz@google.com>
date Wed, 15 Jan 2020 15:07:43 -0800
parents a61287a95dc3
children b7808443ed6a
comparison
equal deleted inserted replaced
44149:50e7ce1f96d1 44150:ff22c76825b9