Jay Soffian <jaysoffian@xxxxxxxxx> writes: > 2. Given a rev-list. This is relatively recent addition to cherry-pick > (7e2bfd3 revert: allow cherry-picking more than one commit, > 2010-06-02). Here's where I'd expect to have a more rebase-like > behavior, using --continue/abort to work through the sequence. But > frankly, I consider 7e2bfd3 a mistake. I think a better implementation > would be to make cherry-pick be plumbing, and re-use rebase's logic > for walking through the series of commit. I'd also love this functionality ... Can basically do it with: # remember current branch name CHERRY_PICK_TARGET git checkout REV_LIST_END git rebase --onto CHERRY_PICK_TARGET REV_LIST_START [+ git rebase --continue etc] but man, is that confusing to remember... I wonder if a wrapper would be robust enough. -Miles -- Cannon, n. An instrument employed in the rectification of national boundaries. -- 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