Re: multiple-commit cherry-pick?
- From
Miles Bader <miles@gnu.org>
- Date
- Nov 7, 2008, 04:38 UTC
- Message-ID
- <fc339e4a0811062038x22e7a3co503f09678f9ff5aa@mail.gmail.com>
- In-Reply-To
- <alpine.LFD.2.00.0811061925300.3451@nehalem.linux-foundation.org>
Show 9 quoted lines
>> git format-patch --full-index --binary --stdout <range...> | git am -3 >> >> This will not work if you want to pick a list, not a range, of >> commits. > > Doesn't "--no-walk" + list commits individually work? > > So it _should_ be possible to pick a list of commits too. Although I think > that git format-patch will reverse the order.
Incidentally, the reason I like a rebase-based solution is that many of the rebase features like -i, --abort, and --continue (after conflict resolution) are very nice for the multi-cherry-pick case too, and I'm already very familiar with their operation from using rebase.
[git-am seems to have some similar features, but I don't know how well they work.]
-Miles
-- Do not taunt Happy Fun Ball.