From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "D. Ben Knoble" <ben.knoble@gmail.com>, Git <git@vger.kernel.org>
Subject: Re: Why does git-grep appear to treat exclude pathspecs differently?
Date: Sat, 02 Aug 2025 10:12:33 -0700 [thread overview]
Message-ID: <xmqqwm7lhcla.fsf@gitster.g> (raw)
In-Reply-To: <20250802094657.GG3711639@coredump.intra.peff.net> (Jeff King's message of "Sat, 2 Aug 2025 05:46:57 -0400")
Jeff King <peff@peff.net> writes:
> PS I didn't even know that we allowed multiple short items or a trailing
> colon until your email! Hidden corners of Git.
But once you think about them, it all makes sense. The trailing
colon can help strange folks who have paths that begin with one of
these strange byte values ;-).
next prev parent reply other threads:[~2025-08-02 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 13:44 Why does git-grep appear to treat exclude pathspecs differently? D. Ben Knoble
2025-07-27 0:16 ` Junio C Hamano
2025-07-30 21:49 ` D. Ben Knoble
2025-08-02 9:46 ` Jeff King
2025-08-02 16:13 ` D. Ben Knoble
2025-08-02 18:52 ` Jeff King
2025-08-03 5:56 ` Junio C Hamano
2025-08-05 18:57 ` Jeff King
2025-08-05 20:06 ` Junio C Hamano
2025-08-02 17:12 ` Junio C Hamano [this message]
2025-08-02 16:14 ` D. Ben Knoble
2025-08-02 17:23 ` 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=xmqqwm7lhcla.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--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).