From: "Jens Tröger" <jens.troeger@light-speed.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Chris Torek <chris.torek@gmail.com>, git@vger.kernel.org
Subject: Re: How does git track history overwrites?
Date: Tue, 26 May 2026 01:20:23 +0200 [thread overview]
Message-ID: <ahTZN7BurySMbEgM@light-speed.de> (raw)
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
prev parent reply other threads:[~2026-05-25 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 23:41 How does git track history overwrites? Jens Tröger
2026-05-25 3:46 ` Chris Torek
2026-05-25 6:51 ` Junio C Hamano
2026-05-25 22:47 ` Jens Tröger
2026-05-25 23:09 ` Junio C Hamano
2026-05-25 23:20 ` Jens Tröger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ahTZN7BurySMbEgM@light-speed.de \
--to=jens.troeger@light-speed.de \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox