From: Brandon Williams <bmwill@google.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] pathspec: removed unnecessary function prototypes
Date: Wed, 14 Sep 2016 12:30:49 -0700 [thread overview]
Message-ID: <CAKoko1qKLPWZEZxzHkrpm-tvz4oLMf=odRLNSRgrHXPxGhHFvg@mail.gmail.com> (raw)
In-Reply-To: <20160914192341.mgpcc35kgmjqunbh@sigill.intra.peff.net>
On Wed, Sep 14, 2016 at 12:23 PM, Jeff King <peff@peff.net> wrote:
> On Tue, Sep 13, 2016 at 11:15:52AM -0700, Jeff King wrote:
> I should have done a better job of not just providing the answer, but
> showing how. The easiest tool here is "git log -S":
>
> git log -1 -p -Scheck_path_for_gitlink
>
> (and then you can see that the whole function went away there).
>
> -Peff
Perfect thanks! There's still a lot of little features like this that
I'm unaware
of so I really appreciate the pointer.
-Brandon
prev parent reply other threads:[~2016-09-14 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 16:52 [PATCH] pathspec: removed unnecessary function prototypes Brandon Williams
2016-09-13 18:15 ` Jeff King
2016-09-13 23:08 ` Junio C Hamano
2016-09-14 19:23 ` Jeff King
2016-09-14 19:30 ` Brandon Williams [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='CAKoko1qKLPWZEZxzHkrpm-tvz4oLMf=odRLNSRgrHXPxGhHFvg@mail.gmail.com' \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).