From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Ralf Thielow" <ralf.thielow@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC] blame: respect "core.ignorecase"
Date: Mon, 10 Sep 2012 16:34:42 -0400 [thread overview]
Message-ID: <20120910203442.GA968@sigill.intra.peff.net> (raw)
In-Reply-To: <7vvcflmxis.fsf@alter.siamese.dyndns.org>
On Mon, Sep 10, 2012 at 01:30:03PM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > If the proposal were instead to add a certain type of pathspec that is
> > case-insensitive[2], that would make much more sense to me. It is not
> > violating git's case-sensitivity because it is purely a _query_ issue.
> > And it is a feature you might use whether or not your filesystem is case
> > sensitive.
> > ...
> > [2] I did not keep up with Duy's work on pathspec magic-prefixes (and I
> > could not find anything relevant in the code or documentation), but
> > it seems like this would be a logical feature to support there.
>
> I think it mostly is in setup.c (look for "Magic pathspec").
Thanks, that helped. I got excited when I saw the "icase" in the
comments and thought it might already be implemented. But it looks like
it is still to be done. :)
-Peff
next prev parent reply other threads:[~2012-09-10 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 17:01 [PATCH/RFC] blame: respect "core.ignorecase" Ralf Thielow
2012-09-09 19:03 ` Johannes Sixt
2012-09-09 19:24 ` Junio C Hamano
2012-09-09 19:45 ` Junio C Hamano
2012-09-11 21:44 ` [PATCH] blame: allow "blame file" in the middle of a conflicted merge Junio C Hamano
2012-09-10 5:57 ` [PATCH/RFC] blame: respect "core.ignorecase" Ralf Thielow
2012-09-10 16:13 ` Jeff King
2012-09-10 20:30 ` Junio C Hamano
2012-09-10 20:34 ` Jeff King [this message]
2012-09-10 21:38 ` Junio C Hamano
2012-09-10 21:41 ` Jeff King
2012-09-10 23:07 ` 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=20120910203442.GA968@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=ralf.thielow@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.
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).