From: Junio C Hamano <gitster@pobox.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Getting pickaxe to perform looser matches, or regex matching
Date: Thu, 07 Jun 2012 10:58:34 -0700 [thread overview]
Message-ID: <7vy5nzgg1h.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACPiFCKyhZPQR+e27Ah5THiPPJy3akajGN5xMwBumP-Wj6JrKQ@mail.gmail.com> (Martin Langhoff's message of "Thu, 7 Jun 2012 12:43:14 -0400")
Martin Langhoff <martin.langhoff@gmail.com> writes:
> I am a regular user of gitk's nice pickaxe search field. But it will often
> fail to find what I am looking for because the part of the string I can
> provide is not the part that changes.
>
> For example, I am looking for patches that change any calls to function
> foo(). I want to match on
>
> - foo(1, 0, 1024)
> + foo(0, 1024, 1)
>
> but I don't know the parameters. As the "pickaxe" sections in gitdiffcore
> and git log manpages indicate, it won't match on -S'foo' because foo itself
> was not added or removed.
>
> A regex like "foo(.*" would work, but pickaxe doesn't seem to take
> regexes, and while I could roll my own wrapper around git-log --patch,
> this sounds like an important and useful variant to pickaxe that is
> missing.
>
> Or that has a hidden switch I haven't found ;-)
Like more expensive -G that was recently added?
next prev parent reply other threads:[~2012-06-07 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 16:43 Getting pickaxe to perform looser matches, or regex matching Martin Langhoff
2012-06-07 17:58 ` Junio C Hamano [this message]
2012-06-07 18:48 ` Martin Langhoff
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vy5nzgg1h.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).