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

Did anyone have trouble learning the idea of local vs. remote branches?

From
Shawn Pearce <spearce@spearce.org>
Date
Nov 7, 2006, 17:24 UTC
Message-ID
<20061107172450.GA26591@spearce.org>

Today I was talking with someone that I collaborate with through Git and they still seemed to not get the idea that all branches in their repository are local, and that at least a 'git fetch' is needed to update the local tracking branches to the version in the central repository that we collaborate through. And this isn't the first time we've had such discussions.

It dawned on me that this person still hasn't grasped the idea behind fetch. A few other users that I know also have commented on how difficult fetch is to learn.

Most seemed to think that fetch would update their working directory, or their current branch, as there is no other way to "download changes from origin". They also seem to expect their local tracking branch to automatically update, especially when invoking `git checkout -b foo tracking-branch`.

Clearly there is a gap in communicating these ideas in a way that they can be understood by users. Of course in at least one case the users just isn't reading any Git documentation and plows ahead as though it were CVS ('cause everything's "just like CVS") *sigh*.

Next: Salikh Zakirov
Message 1 of 9 in “Did anyone have trouble learning the idea of local vs. remote branches?”
  1. Shawn PearceNov 7, 2006
  2. Salikh ZakirovNov 7, 2006
  3. Shawn PearceNov 8, 2006
  4. Matthieu MoyNov 8, 2006
  5. Andreas EricssonNov 8, 2006
  6. Wink SavilleNov 8, 2006
  7. Jakub NarebskiNov 8, 2006
  8. Wink SavilleNov 8, 2006
  9. Jakub NarebskiNov 8, 2006

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.