From: Junio C Hamano <gitster@pobox.com>
To: Tuomas Ahola <taahol@utu.fi>
Cc: "Windl, Ulrich" <u.windl@ukr.de>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Q: .gitignore and asterisk "*"
Date: Tue, 03 Nov 2026 09:13:59 -0800 [thread overview]
Message-ID: <xmqqzevpald4.fsf@gitster.g> (raw)
In-Reply-To: <20261103073317.DATcL%taahol@utu.fi> (Tuomas Ahola's message of "Tue, 3 Nov 2026 09:33:17 +0200")
Tuomas Ahola <taahol@utu.fi> writes:
> Junio C Hamano <gitster@pobox.com> wrote:
>
>> "Windl, Ulrich" <u.windl@ukr.de> writes:
Please trim the lines that do not have any relevance to what you are
going to comment on from your quoted material.
>> - - An asterisk "`*`" matches anything except a slash.
>> - The character "`?`" matches any one character except "`/`".
>> - The range notation, e.g. `[a-zA-Z]`, can be used to match
>> - one of the characters in a range. See fnmatch(3) and the
>> - FNM_PATHNAME flag for a more detailed description.
>> + - An asterisk "`*`" matches string of any length, and a question mark
>
> It's not unreasonable at all to call the empty string "a string of no length",
> so it is still a bit ambiguous whether it qualifies as a string of any length.
> I would suggest s/of any length/of length of zero or more/.
A string of no length falls within the set of strings of any length,
so I do not see any ambiguity there.
"A string of length of zero or more" is a roundabout way to say "any
string" as by definition there is no string of negative length.
Perhaps that is good enough?
next prev parent reply other threads:[~2026-11-03 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 10:46 Q: .gitignore and asterisk "*" Windl, Ulrich
2026-10-30 16:59 ` Junio C Hamano
2026-11-03 7:33 ` Tuomas Ahola
2026-11-03 12:00 ` [EXT] " Windl, Ulrich
2026-11-03 17:13 ` Junio C Hamano [this message]
2026-11-03 17:29 ` Tuomas Ahola
2026-11-03 22:40 ` [PATCH v2] gitignore: rewrite wildcard description 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=xmqqzevpald4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=taahol@utu.fi \
--cc=u.windl@ukr.de \
/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