From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] add core.pathspecGlob config option
Date: Wed, 19 Dec 2012 16:45:01 -0500 [thread overview]
Message-ID: <20121219214500.GA12705@sigill.intra.peff.net> (raw)
In-Reply-To: <7vfw3191bi.fsf@alter.siamese.dyndns.org>
On Wed, Dec 19, 2012 at 01:30:57PM -0800, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > diff --git a/dir.c b/dir.c
> > index 5a83aa7..6e81d4f 100644
> > --- a/dir.c
> > +++ b/dir.c
> > @@ -126,7 +126,7 @@ static int match_one(const char *match, const char *name, int namelen)
> > for (;;) {
> > unsigned char c1 = tolower(*match);
> > unsigned char c2 = tolower(*name);
> > - if (c1 == '\0' || is_glob_special(c1))
> > + if (c1 == '\0' || (core_pathspec_glob && is_glob_special(c1)))
> > break;
> > if (c1 != c2)
> > return 0;
>
> I think you can also do the same to the common_prefix(); we check
> for common leading directory prefix but punt upon seeing a directory
> component that has a glob character, and under the "literal" mode,
> it is not a special character.
Yeah, I think you're right. Will add to my re-roll.
-Peff
next prev parent reply other threads:[~2012-12-19 21:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 20:34 [PATCH] add core.pathspecGlob config option Jeff King
2012-12-19 20:54 ` Junio C Hamano
2012-12-19 21:09 ` Jeff King
2012-12-19 21:50 ` [PATCH] add GIT_PATHSPEC_GLOB environment variable Jeff King
2012-12-19 22:00 ` Junio C Hamano
2012-12-19 22:12 ` Jeff King
2012-12-19 22:16 ` Junio C Hamano
2012-12-19 22:20 ` Jeff King
2012-12-19 22:37 ` Jeff King
2012-12-19 21:30 ` [PATCH] add core.pathspecGlob config option Junio C Hamano
2012-12-19 21:45 ` Jeff King [this message]
2012-12-20 1:28 ` Nguyen Thai Ngoc Duy
2012-12-20 3:13 ` Jeff King
2012-12-20 3:51 ` Junio C Hamano
2012-12-20 3:55 ` Jeff King
2012-12-20 4:06 ` Jeff King
2012-12-20 4:11 ` Jeff King
2012-12-20 5:26 ` 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=20121219214500.GA12705@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).