Junio C Hamano <gitster@xxxxxxxxx> writes: > So perhaps a good way to move forward is to teach "git cherry-pick A..B" > to be a thin wrapper that invokes a new hidden mode of operation added to > "rebase" that is not advertised to the end user. > > I would suggest calling the option to invoke that hidden mode not > "--revisions", but "--reverse" or "--opposite" or something of that > nature, though. It makes "rebase" work in different direction. Intuitively, git rebase --reverse A..B would mean "take the range A..B, and start applying the patches from B, going in reverse order up to A", like "git log --reverse". So, I'd find it misleading. Perhaps "git rebase --cherry-pick A..B" would be a better name. No objection for --opposite either. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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