From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 2/2] pickaxe: allow -i to search in patch case-insensitively
Date: Wed, 29 Feb 2012 03:35:34 -0500 [thread overview]
Message-ID: <20120229083534.GC14181@sigill.intra.peff.net> (raw)
In-Reply-To: <1330474831-9030-3-git-send-email-gitster@pobox.com>
On Tue, Feb 28, 2012 at 04:20:31PM -0800, Junio C Hamano wrote:
> "git log -S<string>" is a useful way to find the last commit in the
> codebase that touched the <string>. As it was designed to be used by a
> porcelain script to dig the history starting from a block of text that
> appear in the starting commit, it never had to look for anything but an
> exact match.
>
> When used by an end user who wants to look for the last commit that
> removed a string (e.g. name of a variable) that he vaguely remembers,
> however, it is useful to support case insensitive match.
>
> When given the "--regexp-ignore-case" (or "-i") option, which originally
> was designed to affect case sensitivity of the search done in the commit
> log part, e.g. "log --grep", the matches made with -S/-G pickaxe search is
> done case insensitively now.
I can't imagine anybody would want to have different case-sensitivity
options for grepping the commit message versus pickaxe. But even if they
do, and we later add options to control them individually, we would
still want the short-and-sweet "-i" to cover the common case of setting
both. So I think the approach is good.
The patch itself looks fine to me.
-Peff
next prev parent reply other threads:[~2012-02-29 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 0:20 [PATCH v2 0/2] "log --regexp-ignore-case -S/-G<string>" Junio C Hamano
2012-02-29 0:20 ` [PATCH v2 1/2] grep: use static trans-case table Junio C Hamano
2012-02-29 8:28 ` Jeff King
2012-02-29 8:51 ` Junio C Hamano
2012-02-29 0:20 ` [PATCH v2 2/2] pickaxe: allow -i to search in patch case-insensitively Junio C Hamano
2012-02-29 8:35 ` Jeff King [this message]
2012-02-29 8:55 ` Junio C Hamano
2012-02-29 9:18 ` Jeff King
2012-02-29 11:40 ` Thomas Rast
2012-02-29 18:05 ` Junio C Hamano
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=20120229083534.GC14181@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).