Re: [BUG] Highly inconsistent diff UI
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Apr 24, 2013, 18:48 UTC
- Message-ID
- <CALkWK0m5Q_e3q6Yg94-K+jU_SS7ovR2wnz-_Nr3cMz_YM=SMDQ@mail.gmail.com>
- In-Reply-To
- <7v38ufer2x.fsf@alter.siamese.dyndns.org>
On Wed, Apr 24, 2013 at 11:41 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Ramkumar Ramachandra <artagnon@gmail.com> writes: > >> What are your thoughts on inventing a new syntax A~B = $(git >> merge-base A B) B which can be used by both range commands like log >> and non-range commands like diff ? (In other words, why shouldn't log >> be able to do this?). > > The idea for a new syntax to denote a merge base may be an > interesting one.
Sorry I wasn't clear. A~B = $(git merge-base A B) B to diff and $(git merge-base A B)..B to log. I don't mind a hybrid command as long as we document it properly. rev-parse will parse it into B ^${git merge-base A B) just fine. Implementation: diff should swap the arguments if the second argument is UNINTERESTING: it already does this :)
Basically, I want to be able to do git log master~rebase.autostash (without having to rebase). I'm also considering making the first argument optional (just git log ~rebase.autostash), and defaulting to mean [nearest fork point].
What do you think?