Re: [PATCH 5/7] revert: do not remove state until sequence is finished
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Dec 14, 2011, 16:02 UTC
- Message-ID
- <CALkWK0nn2mhaP5pwUob2_1ADzNkfP9_ZtUqWnhqWfn7pR9aj7Q@mail.gmail.com>
- In-Reply-To
- <20111210130212.GF22035@elie.hsd1.il.comcast.net>
Hey,
Jonathan Nieder wrote:
Show 6 quoted lines
> [...] > After the recent patch "allow single-pick in the middle of cherry-pick > sequence" we don't need that hack any more. In the new regime, a > traditional "git cherry-pick <commit>" command never looks at > .git/sequencer, so we do not need to cripple "git cherry-pick > <commit>..<commit>" for it any more.
So this is why you needed that "relatively esoteric feature" :P This approach competes with the approach I presented in "New sequencer workflow!" [1], where I use a special case to side-step various sequencer state files: this approach wins on the grounds of simplicity, and I can't see any potential long-term issues with my limited foresight. Do you have any other points of comparison?
[1]: https://github.com/artagnon/git sequencer #; 8a08d09b9
-- Ram