All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: "Nathan W. Panike" <nathan.panike@gmail.com>, git@vger.kernel.org
Subject: Re: Looking for a way to turn off/modify ref disambiguation
Date: Wed, 24 Aug 2011 10:48:46 -0700	[thread overview]
Message-ID: <7vr54apuo1.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4E54C373.1070702@drmicha.warpmail.net> (Michael J. Gruber's message of "Wed, 24 Aug 2011 11:25:07 +0200")

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".

  parent reply	other threads:[~2011-08-24 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 19:26 Looking for a way to turn off/modify ref disambiguation Nathan W. Panike
2011-08-23 21:15 ` Jeff King
2011-08-23 22:03 ` Junio C Hamano
2011-08-24  9:25   ` Michael J Gruber
2011-08-24 16:37     ` Jonathan Nieder
2011-08-24 17:48     ` Junio C Hamano [this message]
2011-08-24  6:54 ` Clemens Buchacher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vr54apuo1.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=nathan.panike@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.