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

Re: How does git track history overwrites?

From
Jens Tröger <jens.troeger@light-speed.de>
Date
May 25, 2026, 23:20 UTC
Message-ID
<ahTZN7BurySMbEgM@light-speed.de>
In-Reply-To
<xmqqfr3fnl2n.fsf@gitster.g>
Hello Junio,
> Sorry, I may have been unclear.  I specifically meant the "grafted,
> " part in the message.  I know how "git log" output looks like ;-)

The “grafted” too was part of the git log output; here is the complete cmd line output:

    /tmp/bla > git log
    commit fda77690955e9b63c6687d8806bafd56a526e45f (grafted, HEAD)
    Author: Adam Johnson <me@adamj.eu>
    Date:   Mon Sep 8 16:31:35 2025 +0100
        Version 1.20.0

On *why* the “grafted” is there in the first place, I suspect that’s got to do with the fetch --depth=1 and that previous history isn’t available in the shallow repo clone.

Cheers, Jens

Previous: Junio C Hamano
Message 6 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.