From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
Kirill Likhodedov <kirill.likhodedov@jetbrains.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git <git@vger.kernel.org>
Subject: Re: git show doesn't work on file names with square brackets
Date: Wed, 10 Feb 2016 16:12:06 -0500 [thread overview]
Message-ID: <20160210211206.GA5755@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqpow4zcwd.fsf@gitster.mtv.corp.google.com>
On Wed, Feb 10, 2016 at 09:35:46AM -0800, Junio C Hamano wrote:
> > IOW, something like this implements the "permissive" thing I wrote above
> > (i.e., be inclusive when seeing if something could plausibly be a
> > filename, but exclusive when complaining that it _could_ be one):
>
> Yup, I think that is probably a better first step.
Thanks. And thank you for the discussion. I read your response last
night and almost just said "OK, let's just scrap my patches, this isn't
worth the trouble". But after reading it again this morning, I think it
forced me to look at the problem in a new way. And while I did scrap my
original patches here, I think the result is accomplishing the same
thing in a much saner way.
Here's what I came up with.
[1/3]: checkout: reorder check_filename conditional
[2/3]: check_filename: tighten dwim-wildcard ambiguity
[3/3]: get_sha1: don't die() on bogus search strings
The first is a minor preparatory cleanup, the second is the meat we've
been discussing, and the third is a bonus, though it has some tradeoffs.
-Peff
next prev parent reply other threads:[~2016-02-10 21:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 13:16 git show doesn't work on file names with square brackets Kirill Likhodedov
2016-02-06 14:21 ` Johannes Schindelin
2016-02-06 14:29 ` Kirill Likhodedov
2016-02-06 16:10 ` Johannes Schindelin
2016-02-06 23:48 ` Duy Nguyen
2016-02-07 15:11 ` Kirill Likhodedov
2016-02-08 5:06 ` Duy Nguyen
2016-02-08 14:15 ` Jeff King
2016-02-08 14:24 ` Jeff King
2016-02-08 15:07 ` Jeff King
2016-02-08 19:35 ` Junio C Hamano
2016-02-08 19:52 ` Jeff King
2016-02-08 20:20 ` Jeff King
2016-02-08 20:56 ` Jeff King
2016-02-08 22:36 ` Junio C Hamano
2016-02-10 15:45 ` Jeff King
2016-02-09 20:37 ` Junio C Hamano
2016-02-10 16:15 ` Jeff King
2016-02-10 17:35 ` Junio C Hamano
2016-02-10 21:12 ` Jeff King [this message]
2016-02-10 21:12 ` [PATCH 1/3] checkout: reorder check_filename conditional Jeff King
2016-02-10 21:31 ` Junio C Hamano
2016-02-10 21:14 ` [PATCH 2/3] check_filename: tighten dwim-wildcard ambiguity Jeff King
2016-02-10 21:19 ` [PATCH 3/3] get_sha1: don't die() on bogus search strings Jeff King
2016-02-10 21:52 ` Junio C Hamano
2016-02-07 15:09 ` git show doesn't work on file names with square brackets Kirill Likhodedov
2016-02-07 17:10 ` Johannes Schindelin
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=20160210211206.GA5755@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kirill.likhodedov@jetbrains.com \
--cc=pclouds@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).