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

Re: How does git track history overwrites?

From
Junio C Hamano <gitster@pobox.com>
Date
May 25, 2026, 23:09 UTC
Message-ID
<xmqqfr3fnl2n.fsf@gitster.g>
In-Reply-To
<074E783A-027D-4C5B-BC44-CC38C53735D7@light-speed.de>
Jens Tröger <jens.troeger@light-speed.de> writes:
Show 11 quoted lines
> Thank you Chris and Junio!
>
>
>> [Junio] Where does this line in your discussion page at GitHub (which is
>> omitted from the post to this list) come from?
>> 
>>    commit fda77690955e9b63c6687d8806bafd56a526e45f (grafted, HEAD)
>> 
>> Are you doing anything funky with .git/info/grafts by any chance?
>
> That line is the result of a `git log` after the `git fetch` I mentioned in my initial email.

Sorry, I may have been unclear. I specifically meant the "grafted, " part in the message. I know how "git log" output looks like ;-)

Previous: Jens TrögerNext: Jens Tröger
Message 5 of 6 in “How does git track history overwrites?”
  1. Jens TrögerMay 24, 2026
  2. Chris TorekMay 25, 2026
  3. Junio C HamanoMay 25, 2026
  4. Jens TrögerMay 25, 2026
  5. Junio C HamanoMay 25, 2026
  6. Jens TrögerMay 25, 2026

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.