On Thu, 22 Feb 2024 14:08:38 +0100, Simon Josefsson wrote:
> Would it make sense to change this to use an inclusive list of permitted
> characters instead? How about checking the field names that is in use
> today, and construct a regexp of permitted symbols out of that?
> Starting point:
> "Niels" == Niels Thykier writes:
Niels> Simon Josefsson:
>> Would it make sense to change this to use an inclusive list of
>> permitted characters instead? How about checking the field names
>> that is in use today, and construct a regexp of permitted symbols
>> out of
> "Sean" == Sean Whitton writes:
Sean> In general, I agree with Santiago. I find Policy's current
Sean> scope and working process effective, and not especially
Sean> ambiguous. I think everyone should read it during the NM
Sean> process, if not sooner.
Sean> Russ has
Simon Josefsson:
Would it make sense to change this to use an inclusive list of permitted
characters instead? How about checking the field names that is in use
today, and construct a regexp of permitted symbols out of that?
Starting point: [A-Za-z][A-Za-z0-9-_]*
/Simon
That is an option and
Would it make sense to change this to use an inclusive list of permitted
characters instead? How about checking the field names that is in use
today, and construct a regexp of permitted symbols out of that?
Starting point: [A-Za-z][A-Za-z0-9-_]*
/Simon
signature.asc
Description: PGP signature
Package: debian-policy
Severity: wishlist
X-Debbugs-Cc: ni...@thykier.net
X-Debbugs-Cc: lintian-ma...@debian.org
X-Debbugs-Cc: de...@lists.debian.org
X-Debbugs-Cc: debian-d...@lists.debian.org
Hi
I am hoping we can agree to some tighter bounds on the field names
followed by relevant tools
6 matches
Mail list logo
