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
Han Jiang <jhcarl0814@gmail.com>
Date
Sep 5, 2024, 22:17 UTC
Message-ID
<CANrWfmRmELO3ZxOZs2i5LvekK+fe3N2zfMebJosmzvkkdrG+AQ@mail.gmail.com>
In-Reply-To
<xmqqplpi5em7.fsf@gitster.g>

Got it, Thanks! I clearly remembered that "using first line" stuff was mentioned in the documentation/progit, but can only find the `git merge` part now. False memory😰.

On Fri, Sep 6, 2024 at 3:01 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 5 quoted lines
>
> 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: Junio C Hamano
Message 3 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.