From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.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 16:45:15 -0300 [thread overview]
Message-ID: <9F0F0FF5-85D8-48E8-B056-F71F56AEB915@gmail.com> (raw)
In-Reply-To: <CAOc+UT0n9pRGur0d4cORU0SMQY-PNs5ekLd=LX9xc940Og+nrQ@mail.gmail.com>
> Hi,
Hi, Max!
> I hate losing the why behind a deleted line.
>
> When you drop code in a review, being able to attach a brief comment
> to that line would save a lot of head-scratching.
Sorry if I misunderstood you, but I can't see the difference of that
to committing empty lines + giving a meaningful commit message.
> Git-ghost – see the remnants of days past in a file.
>
> git-ghost hooks into commit to stash deleted lines in a `.ghost` file
> and enables maintainers to prompt for a short reason. Later you can run:
>
> git ghost view <file>
>
> to see what vanished and why. Blame also becomes easier.
I still don't see the difference of that to git log -- <file>. I
understand that git blame doesn't show what has been deleted, only what
is new and what has changed. But ok, git blame has it's limitations of
being a quick line-wise inspection tool, while more deeper analysis
would require more powerful tools. It looks to me that git log with
some flags would do what you need.
prev parent reply other threads:[~2025-05-23 19:45 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
2025-05-23 19:45 ` Lucas Seiki Oshiro [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=9F0F0FF5-85D8-48E8-B056-F71F56AEB915@gmail.com \
--to=lucasseikioshiro@gmail.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).