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

Re: New way of tracking remote branches -- question

From
Theodore Tso <tytso@mit.edu>
Date
Jan 6, 2007, 14:10 UTC
Message-ID
<20070106141032.GB28972@thunk.org>
In-Reply-To
<7v8xghariv.fsf@assigned-by-dhcp.cox.net>
On Fri, Jan 05, 2007 at 05:11:04PM -0800, Junio C Hamano wrote:
Show 6 quoted lines
>  * Your heads/ namespace is of your own.  The repository clone
>    sets up arranges the master branch to start from the same
>    commit as where you cloned from, and sets up so that changes
>    made on the master at the remote is merged into your master,
>    but that is merely a convention that was deemed as the most
>    common and the most convenient.

The other nice thing about the new scheme is that if new branches appear in the remote repository, they automatically show up in remote/origin/*. Before, if new branches showed up after the initial clone, you'd never know about it and it wouldn't be possible to automatically create new branches in heads/ since it might conflict with an originally existing branch in the local namespace. So IMHO, the separation of namespace is definitely a good thing.

						- Ted
Previous: Steven GrimmNext: Luben Tuikov
Message 9 of 13 in “New way of tracking remote branches -- question”
  1. Luben TuikovJan 5, 2007
  2. Junio C HamanoJan 5, 2007
  3. Junio C HamanoJan 5, 2007
  4. Luben TuikovJan 6, 2007
  5. Luben TuikovJan 6, 2007
  6. Junio C HamanoJan 5, 2007
  7. Junio C HamanoJan 6, 2007
  8. Steven GrimmJan 6, 2007
  9. Theodore TsoJan 6, 2007
  10. Luben TuikovJan 9, 2007
  11. Junio C HamanoJan 9, 2007
  12. Luben TuikovJan 9, 2007
  13. Martin LanghoffJan 9, 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.