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

Re: understanding how remote tracking works

From
Michael Witten <mfwitten@gmail.com>
Date
Aug 9, 2010, 02:13 UTC
Message-ID
<AANLkTi=usaZGfOM67acmdAWwvbHe_eHyjmRLGmdTYNaC@mail.gmail.com>
In-Reply-To
<AANLkTinktpx-rXj1K0BSy0Qwo62SEGFAJWvhKo0nJq=i@mail.gmail.com>
On Sun, Aug 8, 2010 at 20:53, Geoff Russell <geoffrey.russell@gmail.com> wrote:
> I'm working my way through Jon Loeliger's Git book and it's
> confusing when the actual behaviour differs from that in the book

This probably results from the git culture's conflation (or should I say confusion?) of low-level and high-level representations and commands.

Previous: Geoff RussellNext: Jonathan Nieder
Message 4 of 11 in “understanding how remote tracking works”
  1. Geoff RussellAug 9, 2010
  2. Ralf EbertAug 9, 2010
  3. Geoff RussellAug 9, 2010
  4. Michael WittenAug 9, 2010
  5. Jonathan NiederAug 9, 2010
  6. Geoff RussellAug 9, 2010
  7. Junio C HamanoAug 9, 2010
  8. Jonathan NiederAug 9, 2010
  9. discarding refs/original/* after filter-branch (Re: understanding how remote tracking works)Jonathan Nieder, Aug 9, 2010
  10. Documentation: add a FILES section for show-refJonathan Nieder, Aug 9, 2010
  11. Junio C HamanoAug 9, 2010

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.