Re: Looking for a way to turn off/modify ref disambiguation

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 24, 2011, 17:48 UTC
Message-ID: <7vr54apuo1.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4E54C373.1070702@drmicha.warpmail.net>

Michael J Gruber <git@drmicha.warpmail.net> writes:

> I haven't come across advice like that....
> I consider that advice very bad indeed:
>
> If "origin..master" is resolved to...

Perhaps origin..master was a bad example for you [*1*]; but the point is you can say "origin" to mean the commit at the tip of the remote tracking branch that the repository you cloned from deemed as its primary branch anywhere we expect a commit on the command line.

So if you do not like "log origin..master", then say "git log origin" instead and the point still stands.

[Footnote]

*1* "origin..master" is still a perfectly good example in tutorials to teach people who use the workflow with a single at the central repository, i.e. the simplest for esapee from CVS/SVN. You may have "frotz" topic and "nitfol" topic branches locally cooking your own changes, and you can measure their progress against the central repository with "origin..frotz" and "origin..nitfol".