From: Michael J Gruber <git@drmicha.warpmail.net>
Date: Thu, 24 Feb 2011 12:24:57 GMT
Subject: Re: [PATCH] completion: complete "git diff ...branc<TAB>"
Message-ID: <4D664E19.5080804@drmicha.warpmail.net>
In-Reply-To: <7vlj1677gz.fsf@alter.siamese.dyndns.org>

Junio C Hamano venit, vidit, dixit 23.02.2011 22:43:
> While doing a final sanity check before merging a topic Bsomething, it is
> a good idea to review what damage Bsomething branch would make, by running:
> 
>     $ git diff ...Bsomething
> 
> I however find myself often typing "git diff ...B<TAB>", seeing nothing
> happening and then repeatedly hitting <TAB>, saying "huh? <TAAAAAAAAB>!".
> 
> This change would hopefully help me, and others like me.
> 
> Even though there is no point in supporting "git diff A..B" (you can say
> "git diff A B" just fine), but reusing complete-revlist was the easiest
> and that form is supported as a benign but not so useful side effect.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> 
>  * I sent this out a while ago and have been using it ever since, but
>    totally forgot about it.  Likes, dislikes, alternatives?

Likes

Reminds me fo the following: Typing

git log origin/next@{1}..o<TAB>

gives

git log origin/next{1}..o

WTF? Completion eats at babies!

Michael