From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] git related v0.3
Date: Wed, 26 May 2021 19:58:02 -0500 [thread overview]
Message-ID: <60aeee9a14f13_770c208cd@natae.notmuch> (raw)
In-Reply-To: <CACBZZX6gOeTrLJwL-Zp5hEEbWCipioPgNKt7Tc41ixcQLQshiw@mail.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> The general heuristic I use, which I've found to be much better than
> git-blame is:
>
> 1. Find substrings of code I'm directly removing/altering, and
> functions I'm removing/altering
> 2. Do git log --reverse -p -S'<substr>' (maybe with -- file) for a
> list of substrings
v1.0 of git-related has a similar tool: git-who, which you can use to do
precisely that:
git who -S'<substr>'
Cheers.
--
Felipe Contreras
prev parent reply other threads:[~2021-05-27 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 0:36 [ANNOUNCE] git related v0.3 Felipe Contreras
2014-05-19 10:11 ` Ævar Arnfjörð Bjarmason
2014-05-19 21:27 ` Felipe Contreras
2021-05-27 0:58 ` Felipe Contreras [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=60aeee9a14f13_770c208cd@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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).