From: Nikolaus Schuetz <nikolauspschuetz@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH v2] t1402: test forbidden characters in refnames
Date: Sun, 23 Aug 2026 09:15:11 -0500 [thread overview]
Message-ID: <20260823141600.74820-1-nikolauspschuetz@gmail.com> (raw)
In-Reply-To: <xmqq5x13stxt.fsf@gitster.g>
> Many funny characters are not allowed between 'foo' and 'bar', but
> are there characters other than dot that are not allowed at the
> beginning or at the end (e.g., "refs/heads/foo." and "foo.lock")?
>
> IOW are we testing exhaustive now?
No -- dot is the only character with position-specific rules,
and every other character in the forbidden set is rejected
anywhere in a component.
The file already exercises each of those rules on its own -- the
leading/trailing-dot, ".lock", empty-component, single-level and
--normalize cases are all present. So this isn't reaching for
exhaustiveness; the coverage was already broad, and this just
fills the untested gap -- of the "forbidden anywhere" characters,
only "?", "\" and ".." were tested embedded, so I folded the rest
into the loop.
Thanks,
Nikolaus
prev parent reply other threads:[~2026-08-23 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 20:43 [PATCH] t1402: test forbidden characters in refnames Nikolaus Schuetz via GitGitGadget
2026-08-19 11:20 ` Patrick Steinhardt
2026-08-19 20:22 ` Junio C Hamano
2026-08-20 14:46 ` Nikolaus Schuetz
2026-08-20 22:20 ` [PATCH v2] " Nikolaus Schuetz via GitGitGadget
2026-08-21 9:29 ` Junio C Hamano
2026-08-23 14:15 ` Nikolaus Schuetz [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=20260823141600.74820-1-nikolauspschuetz@gmail.com \
--to=nikolauspschuetz@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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