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

Terminology question about remote branches.

From
David Kastrup <dak@gnu.org>
Date
Aug 4, 2007, 10:55 UTC
Message-ID
<854pjfin68.fsf@lola.goethe.zz>

I am trying to dig through man-pages and user manual and trying to match them with reality. I seem to have a hard time. My current understanding (which definitely differs from the documented state) is that there are two types of branches, local and remote branches, and both types of branches can be remote-tracking (it may not be possible to have a non-remote-tracking remote branch, though).

A local branch is one with a local branch head. In contrast, checking out a remote branch, while possible, leaves one with a detached head.

"remote-tracking" basically means that git-pull will update the branch according to changes in the remote repository.

Creating a branch using git-branch or git-checkout will always create a local branch which may or may not be remote-tracking according to the --no-track or --track options.

So there are basically three types of branches in a repository that I can see:

local branch, not remote-tracking local branch, remote-tracking remote branch, remote-tracking

The way to add a remote branch basically is not via git-branch or git-checkout -b (those always create local branches), but by editing .git/config.

Is this understanding correct or did I get things completely wrong? Because there is little sense in myself working on changing the documentation if I have not understood the situation.

Also, the documentation currently uses "remote-tracking" interchangeably for "local branch, remote-tracking" and "remote branch, remote-tracking", at some times claiming that one can locally switch to a "remote-tracking" branch, at other times not.

So the terminology seems fuzzy at the moment, and my attempt to clear it up might not be the preferred way of doing it.

Thanks,
-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Next: Jeff King
Message 1 of 46 in “Terminology question about remote branches.”
  1. David KastrupAug 4, 2007
  2. Jeff KingAug 4, 2007
  3. David KastrupAug 4, 2007
  4. Lars HjemliAug 4, 2007
  5. David KastrupAug 4, 2007
  6. Lars HjemliAug 4, 2007
  7. David KastrupAug 4, 2007
  8. David KastrupAug 4, 2007
  9. Lars HjemliAug 4, 2007
  10. David KastrupAug 4, 2007
  11. Lars HjemliAug 4, 2007
  12. Jeff KingAug 5, 2007
  13. Julian PhillipsAug 4, 2007
  14. David KastrupAug 4, 2007
  15. Julian PhillipsAug 4, 2007
  16. David KastrupAug 4, 2007
  17. Theodore TsoAug 4, 2007
  18. David KastrupAug 5, 2007
  19. Jeff KingAug 5, 2007
  20. David KastrupAug 5, 2007
  21. Jeff KingAug 5, 2007
  22. David KastrupAug 5, 2007
  23. Jeff KingAug 5, 2007
  24. Jakub NarebskiAug 4, 2007
  25. SeanAug 4, 2007
  26. David KastrupAug 4, 2007
  27. SeanAug 4, 2007
  28. David KastrupAug 4, 2007
  29. Jeff KingAug 5, 2007
  30. Jeff KingAug 5, 2007
  31. Steffen ProhaskaAug 5, 2007
  32. Jeff KingAug 5, 2007
  33. David KastrupAug 5, 2007
  34. Jeff KingAug 5, 2007
  35. David KastrupAug 5, 2007
  36. Jeff KingAug 5, 2007
  37. Theodore TsoAug 5, 2007
  38. David KastrupAug 5, 2007
  39. Randal L. SchwartzAug 5, 2007
  40. SeanAug 5, 2007
  41. Jeff KingAug 5, 2007
  42. Junio C HamanoAug 5, 2007
  43. Steffen ProhaskaAug 5, 2007
  44. Julian PhillipsAug 5, 2007
  45. David KastrupAug 5, 2007
  46. Julian PhillipsAug 5, 2007

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.