Thread (9 messages) flat view 9 messages, 5 authors, 2016-06-15

Re: remote branches, and branch names in general

From: Jeff King <hidden>
Date: 2016-06-15 22:46:19

On Tue, Mar 03, 2009 at 09:58:55AM +0100, Markus Heidelberg wrote:
quoted
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.
Oh, indeed. Thanks for pointing it out.

Though I think this may be part of what people mean when they say git
documentation sucks. I had no idea where to look for such a thing, and
it turns out it is in the manpage for a plumbing command that in theory
I should never have to use.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help