Git development
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: Jeff King <peff@peff.net>
Cc: Jakub Narebski <jnareb@gmail.com>,
	John Dlugosz <JDlugosz@tradestation.com>,
	git@vger.kernel.org
Subject: Re: remote branches, and branch names in general
Date: Tue, 3 Mar 2009 09:58:55 +0100	[thread overview]
Message-ID: <200903030958.56150.markus.heidelberg@web.de> (raw)
In-Reply-To: <20090303041631.GB18136@coredump.intra.peff.net>

Jeff King, 03.03.2009:
> On Mon, Mar 02, 2009 at 04:38:42PM -0800, Jakub Narebski wrote:
> 
> > > I see the remote branches with names of the form remotes/pub/name where
> > > pub is the nickname of the place I pull from.  To specify such branches,
> > > must I always spell it out with the leading "remotes/", or can that be
> > > shorted or implied somehow?  
> > 
> > You usually can omit "remotes/" prefix, and just use
> > "<remote>/<branch>" (or even "<remote>" for "<remote>/HEAD"). You need
> > it only if there is need for disambiguation.
> 
> Yes. I don't know if they are documented anywhere, but the complete
> lookup order is:
> 
>   $ git grep -h -A8 ref_rev_parse_rules refs.c
>   const char *ref_rev_parse_rules[] = {
>           "%.*s",
>           "refs/%.*s",
>           "refs/tags/%.*s",
>           "refs/heads/%.*s",
>           "refs/remotes/%.*s",
>           "refs/remotes/%.*s/HEAD",
>           NULL
>   };

Documented in git-rev-parse -> specifying revisions.

Markus

  reply	other threads:[~2009-03-03  9:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 20:46 remote branches, and branch names in general John Dlugosz
2009-03-03  0:38 ` Jakub Narebski
2009-03-03  4:16   ` Jeff King
2009-03-03  8:58     ` Markus Heidelberg [this message]
2009-03-03  9:05       ` Jeff King
2009-03-03 15:52     ` John Dlugosz
2009-03-03 16:11       ` Jeff King
2009-03-03 19:32         ` Jay Soffian
2009-03-04 10:29           ` Jeff King

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=200903030958.56150.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --cc=JDlugosz@tradestation.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=peff@peff.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox