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

Re: [Newbie] How to *actually* get rid of remote tracking branch?

From
Jakub Narebski <jnareb@gmail.com>
Date
Nov 13, 2007, 22:42 UTC
Message-ID
<200711132342.45280.jnareb@gmail.com>
In-Reply-To
<473A262B.4010205@op5.se>
Andreas Ericsson wrote:
Show 15 quoted lines
> This is what I've got in Documentation/glossary.txt so far:
> 
> [[def_remote_tracking_branch]]remote-tracking branch:
>     A "remote-tracking branch" is a branch set up to track the
>     state of a branch in a remote repository which the user has named. 
>     These branches follow exactly the same rules as the branches which
>     reside in the remote repository, except that they are manipulated
>     by `git fetch` instead of `git push`. That is, they can only be
>     updated if the update would result in a 
>     <<def_fastforward,fast forward>>, or if the user supplies the 
>     '--force' option. 
>     They cannot be checked out or committed to by users, but serve
>     solely as local reference-pointers to their corresponding branches
>     in the remote repository.
>     The most common example of a remote-tracking branch is origin/master.
If user supplies '--force' option, ur uses '+<src>:<dst>' refspec
('+<remote branch>:<remote-tracking branch>').
 
> It's a bit long-winded. Anyone got any improvements?
Long winded is good. Well, long is good.
I would add that remote-tracking branches reside in refs/remotes/<remote>.

I would skip the part about `git push`, and just say that they are updated on fetch (`git fetch` or `git pull`).

-- 
Jakub Narebski
Poland
Previous: Andreas EricssonNext: J. Bruce Fields
Message 22 of 28 in “[Newbie] How to *actually* get rid of remote tracking branch?”
  1. Sergei OrganovNov 13, 2007
  2. Jakub NarebskiNov 13, 2007
  3. Sergei OrganovNov 13, 2007
  4. Johannes SchindelinNov 13, 2007
  5. Sergei OrganovNov 13, 2007
  6. Johannes SchindelinNov 13, 2007
  7. Sergei OrganovNov 13, 2007
  8. Jan HudecNov 17, 2007
  9. Jakub NarebskiNov 13, 2007
  10. Steffen ProhaskaNov 13, 2007
  11. Jakub NarebskiNov 13, 2007
  12. osv@javad.comNov 13, 2007
  13. Lars HjemliNov 13, 2007
  14. Sergei OrganovNov 13, 2007
  15. Steffen ProhaskaNov 13, 2007
  16. Jan HudecNov 17, 2007
  17. Improve description of git-branch -d and -D in man page.Jan Hudec, Nov 17, 2007
  18. Sergei OrganovNov 19, 2007
  19. Sergei OrganovNov 13, 2007
  20. Andreas EricssonNov 13, 2007
  21. Andreas EricssonNov 13, 2007
  22. Jakub NarebskiNov 13, 2007
  23. J. Bruce FieldsNov 13, 2007
  24. Junio C HamanoNov 13, 2007
  25. Andreas EricssonNov 14, 2007
  26. Steffen ProhaskaNov 14, 2007
  27. Sergei OrganovNov 13, 2007
  28. Jakub NarebskiNov 13, 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.