Re: [PATCH RFC] rebase: add --revisions flag
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Dec 9, 2009, 13:30 UTC
- Message-ID
- <vpqiqcgp95t.fsf@bauges.imag.fr>
- In-Reply-To
- <7vfx7lcj18.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 7 quoted lines
> 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/