From: Daniel Barkalow <barkalow@iabervon.org>
Date: Fri, 07 Nov 2008 20:10:32 GMT
Subject: Re: [minor usability suggestion] git rebase <upstream> --onto <newbase> ?
Message-ID: <alpine.LNX.1.00.0811071504110.19665@iabervon.org>
In-Reply-To: <7vej1ngztd.fsf@gitster.siamese.dyndns.org>

On Fri, 7 Nov 2008, Junio C Hamano wrote:

> Ingo Molnar <mingo@elte.hu> writes:
> 
> >  earth4:~/tip> git rebase 685aebb --onto linus
> >  Current branch core/urgent is up to date.
> > ...
> > For example "git log" is exemplary in this area as it accepts just 
> > about any permutation of parameters thrown at it, ...
> 
> Not really.
> 
> There may be oddball commands whose parameter order have been established
> differently long before "git log" came, but almost all of them now use the
> same convention used by the "git log" family, which is flags/options then
> revs (and then paths if the operation makes sense with paths).  And rebase
> is not one of the oddball ones.
> 
> Your "rebase" example is a rev then a flag/option, which is not how any
> other git command take its command line parameters.

"git log origin/master -p" works, though. It's paths, not revisions, that 
can't appear before options (or revisions).

	-Daniel
*This .sig left intentionally blank*