On Fri, 13 Oct 2023, Arthur Zamarin wrote:

The paragraph should be of format ``Removal on ${DATE}. ${BUGS-LIST}``, where
the date is RFC-3339 full-date format, meaning ``YYYY-MM-DD``, and the bugs >>> list is of the `bugs list`_ format. The listed bugs should include the
last-rite bug opened, and potentially more relevant bugs which weren't listed
in the explanation paragraphs.

Does this mean that only the first of the following entries would be
valid?

# Removal on 2023-11-13. Bugs #678901, #890123
# Removal on 2023-11-13, bugs #678901, #890123.
# Removal on 2023-11-13. Bugs #678901 #890123

IMHO that would be too restrictive. Punctuation shouldn't be significant
there. (This doesn't preclude _recommending_ one of the variants.)

Your current interpretation was correct. My main goal is to define a "precise" format, so it easy to parse for render of mask (i.e. soko). I
also think we have nothing to gain from allowing "," instead of "."
after removal date, but not that I care. Same for bugs-list, I'm fine
with making the "," optional, but I want us to define a "precise regex"
so we have consistent format for important bits of mask message. Does
this seem good enough for you?

BUGS-LIST ::= [Bb]ugs? #\d+(,? +#\d+)*

Make this one either "[Bb]ugs? #\d+(,? #\d+)*" (which I'd prefer)
or "[Bb]ugs? +#\d+(,? +#\d+)*". That is, same number of spaces in both locations.

LAST-RITE ::= Removal on {DATE}[.,]? +{BUGS-LIST}.?

Looks good. Adding " *" at the end won't harm, in case someone will
leave spurious whitespace at the end of the line.

Ulrich

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQFDBAEBCAAtFiEEtDnZ1O9xIP68rzDbUYgzUIhBXi4FAmUpj7EPHHVsbUBnZW50 b28ub3JnAAoJEFGIM1CIQV4uiZAH/i4jhD2chnIpocvhpStTglNvqxdq7yJ8/a8B oNXSOIpuYWCi4ExREZL7YCkq7t9UlAJt47lrgHYFv6Bir7K0Hv77Du5MQKCNlzhT VhcDFIA8KSPwKsKY8xxZM/5VPegf6B8ND5A6b5lbfURiuUEU1MYqvRXq6mh9O7rX 2FvvAcim2jNRxz61Yr5S+gZP55q0RLtK3za1G/kikgPTnDTDKENCVraJHR1qi0gK +gxCm0rIZWEaHgo2QBlkiZsgSvhfggruf8QV43EiSP8tF5Lq6y3uYNHJBx0QRGAQ MMhP+BdbEvpCPrdQSYGOzhAYmNB8a3sg9fbiu3l/aPaM5+2iOd0=+wfe
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Copy: [email protected]
Copy: [email protected]

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------YDTqic04tRcnuhRuKF7MHc5Z
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 13/10/2023 21.42, Ulrich Mueller wrote:

BUGS-LIST ::= [Bb]ugs? #\d+(,? +#\d+)*

Make this one either "[Bb]ugs? #\d+(,? #\d+)*" (which I'd prefer)
or "[Bb]ugs? +#\d+(,? +#\d+)*". That is, same number of spaces in both locations.

OK, would be hard to define it correctly in the BNF, but will just use
{n} syntax to pass the intent, and explain in English what you said here
(same amount of spaces between "things", with preferred n=1.

LAST-RITE ::= Removal on {DATE}[.,]? +{BUGS-LIST}.?

Looks good. Adding " *" at the end won't harm, in case someone will
leave spurious whitespace at the end of the line.

Well, earlier we prohibit trailing whitespace, so it would indeed bring
harm xD

Ulrich

--
Arthur Zamarin
[email protected]
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)


--------------YDTqic04tRcnuhRuKF7MHc5Z--

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE/axFlFuH2ptjtO5EAqCvUD0SBQQFAmUpnBIACgkQAqCvUD0S BQSVhQf/fWuneXU4+bcXqK909409fNbMYXFmawXKdJUzwiYcBaHwMfRxoSZNr3Kb lCKUpLON6d4eIv3YDhJAa9V8g3U7RZQjsMtJw0Sw4zGpvlmTzd2kchStLJrB/1kk lKIQNI14L2FhOtvJXV+t+G/Zg2ltOZLhRa0+4kw4UuwYw+MrPBcg1Vaa318p6Mmw QW9oO29iTKbpM18GG6qqTxEyoff+jS4OMvw4MCPgyVhKctbfJm4PP1wKeqNDdk8S AHbi8mj+6af2HgbK5fjOQU9+rshRdEFEAorwDpsY3I7r6Lkq6RNT89SQMzi+O3gD lV3u9AVl6MHxHTeCNptdxNJ9JYtYhA==
=gJlp
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 13 Oct 2023, Arthur Zamarin wrote:

Make this one either "[Bb]ugs? #\d+(,? #\d+)*" (which I'd prefer)
or "[Bb]ugs? +#\d+(,? +#\d+)*". That is, same number of spaces in both
locations.

OK, would be hard to define it correctly in the BNF, but will just use
{n} syntax to pass the intent, and explain in English what you said here (same amount of spaces between "things", with preferred n=1.

I think you've misunderstood me. I meant that the regex should either
match exactly one space, but then in both places (after "[Bb]ugs?" and
after the comma). Or, it should allow an arbitrary number of spaces
in both places.

Ulrich

-----BEGIN PGP SIGNATURE-----

iQFDBAEBCAAtFiEEtDnZ1O9xIP68rzDbUYgzUIhBXi4FAmUpnrMPHHVsbUBnZW50 b28ub3JnAAoJEFGIM1CIQV4uzNQIAK8vX6YQn7WCQynJcsCHAKlIJ8IdOJQQlwsZ aF/zO/OADKPjJ9WC0q1y4dtRGULVQgGgCMZeAzWCY+xTPNX0KfEETIgb7XhGndwm +QmFVO5XIM9L2RNWdHYA52e4DZBwKgQdTiCuvD1gM+8SgIlIRof67qQz+K6O6bm4 YGWJVmt4+ouOKlHEGy+QIZZ32BwLpOLo6tm+9BsAKCtJjCXiLtdiGKMwcAPlpbWw 8JX4kDP/R5g9tjWZ6HT+QPsCwc9K52tVEy3Eao6m29VOnVrKU85bJgEstt78g7dY 4eB6hKjx7htmLz3xQ+E/JGvRTYgcPNibg/MZN3IZ9CmlkD9fQmc=
=EXZe
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)