From: Junio C Hamano <gitster@pobox.com>
To: Max Rhodin <max@ux.se>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-ghost: preserve “why” on deleted lines
Date: Fri, 23 May 2025 10:24:44 -0700 [thread overview]
Message-ID: <xmqqh61bxmsj.fsf@gitster.g> (raw)
In-Reply-To: <CAOc+UT0n9pRGur0d4cORU0SMQY-PNs5ekLd=LX9xc940Og+nrQ@mail.gmail.com> (Max Rhodin's message of "Fri, 23 May 2025 14:32:28 +0200")
Max Rhodin <max@ux.se> writes:
> Comments?
Would running "git blame" in reverse work for your use case?
Tracing deleted contents is much harder than tracing contents in the
current revision, simply because you have to find where to start
digging. In order to find where the contents were removed, you
first need to know what exact contents you are looking for (which
by definition you cannot do with the current revision), and then you
need to know what revision had that code.
What I do in practice is to randomly check out an old revision to
find sufficiently old one that still contains the contents ("git
bisect" can help), and then go from there.
next prev parent reply other threads:[~2025-05-23 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 12:32 [RFC] git-ghost: preserve “why” on deleted lines Max Rhodin
2025-05-23 17:24 ` Junio C Hamano [this message]
2025-05-23 19:45 ` Lucas Seiki Oshiro
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=xmqqh61bxmsj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=max@ux.se \
/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;
as well as URLs for NNTP newsgroup(s).