Ramkumar Ramachandra wrote: > But: > > git cherry-pick foo > ..conflict.. > git sequencer --abort > error: No sequencer operation in progress. I mentioned this before: "git sequencer --abort" could notice that CHERRY_PICK_HEAD exists and .git/sequencer does not and act accordingly. > In a nutshell, the problem we're facing: We persist part of the > continuation data outside the sequencer's knowledge, and part of it > inside. For backward compatibility, we can't move the former part > into the sequencer. Why can't it become the sequencer's responsibility, FWIW? That's an implementation detail. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html