Re: [PATCH 7/7] sequencer: Remove sequencer state after final commit
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 18, 2011, 20:42 UTC
- Message-ID
- <7vvctu8naf.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20110818191812.GG30436@elie.gateway.2wire.net>
Jonathan Nieder <jrnieder@gmail.com> writes:
> One part I'm handwaving is what to do about commands like "git > cherry-pick foo^..foo" which use a commit range that only happens to > contain one commit.
Historically cherry-pick took a single commit from the command line. That can easily be distinguished from a "set that ended up with one positive commit after walking the history". I think you can even check before triggering the revision walking machinery in the first place.