Re: [PATCH 7/7] sequencer: Remove sequencer state after final commit
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Aug 18, 2011, 20:12 UTC
- Message-ID
- <20110818201220.GJ30436@elie.gateway.2wire.net>
- In-Reply-To
- <CALkWK0nV35gNFM2NW-FrwBLnvFzmWDdARZk0Xy6LT8c2UE0fAw@mail.gmail.com>
Ramkumar Ramachandra wrote:
Show 6 quoted lines
> 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.