Phillip Wood <phillip.wood...@gmail.com> writes: > Avoid this > potential problem by removing the sequencer state if we're committing or > resetting the final pick in a sequence.
The use-case story before this conclusion only mentioned "commit" that concluded the multi-step cherry-pick/revert, and never talked about "reset", which made my eyebrows to rise. As a part of "reset", we have already been removing CHERRY_PICK_HEAD and REVERT_HEAD, so "git reset" during a conflicted "cherry-pick" for example is already destructive and the user can no longer get back to continuing the cherry-pick anyway after running it, even without this patch. So from that point of view, it does make sense to remove the other sequencer states at the same time. Thanks.
