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

Re: `git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 5, 2024, 15:01 UTC
Message-ID
<xmqqplpi5em7.fsf@gitster.g>
In-Reply-To
<CANrWfmSMbR+8oGsCzOygBA0sFSmMwUmCy=qQEsa16RWcztYaQA@mail.gmail.com>

This is totally expected. FETCH_HEAD is only special to "git merge". When FETCH_HEAD is used as if it were a ref, everybody else uses only the first entry.

Previous: Han JiangNext: Han Jiang
Message 2 of 3 in “`git log FETCH_HEAD` only logs whatever happens to be the first among the fetched refs (instead of all the fetched refs)”
  1. Han JiangSep 5, 2024
  2. Junio C HamanoSep 5, 2024
  3. Han JiangSep 5, 2024

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.