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@xxxxxxxxx>
> ---
>
> * 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
--
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