From: Junio C Hamano <gitster@pobox.com>
To: "Jens Tröger" <jens.troeger@light-speed.de>
Cc: Chris Torek <chris.torek@gmail.com>, git@vger.kernel.org
Subject: Re: How does git track history overwrites?
Date: Tue, 26 May 2026 08:09:04 +0900 [thread overview]
Message-ID: <xmqqfr3fnl2n.fsf@gitster.g> (raw)
In-Reply-To: <074E783A-027D-4C5B-BC44-CC38C53735D7@light-speed.de> ("Jens Tröger"'s message of "Tue, 26 May 2026 08:47:10 +1000")
Jens Tröger <jens.troeger@light-speed.de> writes:
> 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 ;-)
next prev parent reply other threads:[~2026-05-25 23:09 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 [this message]
2026-05-25 23:20 ` Jens Tröger
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=xmqqfr3fnl2n.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=jens.troeger@light-speed.de \
/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