git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: "remote-tracking branch"?

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 11, 2012, 16:31 UTC
Message-ID
<7vr4tl7qu3.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4FD6068D.1010509@xiplink.com>
Marc Branchaud <marcnarc@xiplink.com> writes:
Show 6 quoted lines
> When I first read this I was confused by the term "remote-tracking branch".
> I see that the docs for "git remote" and "git branch" use this term for
> branches like 'origin/master', as does the glossary.
> ...
> I feel my interpretation is reinforced by the --track/--no-track options in
> "git branch".

They were added long after "remote tracking branch" terminology has been established to mean the copies of last observed values of refs at remotes, and back then nobody noticed that these misnamed options were potential sources of this kind of confusion. If anything, these options need to be renamed if you want to avoid confusion.

Unfortunately, no concensus terminology for them exist; I find myself calling them "the branch you integrate with upstream's master", "the branch you forked from origin's topic", etc.

Previous: Marc BranchaudNext: Junio C Hamano
Message 2 of 3 in “"remote-tracking branch"?”
  1. Marc BranchaudJun 11, 2012
  2. Junio C HamanoJun 11, 2012
  3. Junio C HamanoJun 11, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.