From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jan Engelhardt <jengelh@inai.de>, git@vger.kernel.org
Subject: Re: `git grep` is too picky about option parsing
Date: Mon, 07 Dec 2020 11:35:16 -0800 [thread overview]
Message-ID: <xmqqtusx9zpn.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <X856rSHziQcmr/zX@coredump.intra.peff.net> (Jeff King's message of "Mon, 7 Dec 2020 13:55:41 -0500")
Jeff King <peff@peff.net> writes:
> would be sad to lose it. (I don't use it with grep, but my standard perl
> invocation is "perl -lpe 'some script'"; another common one is "tar xvf
> foo.tar").
Heh, "tar" is a different breed, isn't it? It can have a clump of
single letter options among which more than one take parameter.
> And it works now (obviously not in the case we're discussing, but in
> other cases that don't run afoul of the typo fix), so I think people
> would see that as a regression.
Sure.
prev parent reply other threads:[~2020-12-07 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 22:12 `git grep` is too picky about option parsing Jan Engelhardt
2020-12-07 17:02 ` Jeff King
2020-12-07 18:46 ` Junio C Hamano
2020-12-07 18:55 ` Jeff King
2020-12-07 19:35 ` Junio C Hamano [this message]
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=xmqqtusx9zpn.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jengelh@inai.de \
--cc=peff@peff.net \
/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).