From: Arthur Zamarin <arthurzam@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, glep@gentoo.org
Subject: Re: [gentoo-dev] Re: [DRAFT v2] GLEP 84: Standard format for package.mask files
Date: Fri, 13 Oct 2023 22:35:45 +0300 [thread overview]
Message-ID: <1aee1edd-2e5f-4aae-8b1a-604fa6b881f5@gentoo.org> (raw)
In-Reply-To: <uedhys6ry@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 863 bytes --]
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
arthurzam@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-10-13 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 14:11 [gentoo-dev] [DRAFT v2] GLEP 84: Standard format for package.mask files Arthur Zamarin
2023-10-13 16:06 ` [gentoo-dev] " Ulrich Mueller
2023-10-13 16:30 ` Arthur Zamarin
2023-10-13 18:42 ` Ulrich Mueller
2023-10-13 19:35 ` Arthur Zamarin [this message]
2023-10-13 19:46 ` Ulrich Mueller
2023-10-13 18:49 ` [gentoo-dev] " Ulrich Mueller
2023-10-13 19:32 ` Arthur Zamarin
2023-10-13 19:43 ` Ulrich Mueller
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=1aee1edd-2e5f-4aae-8b1a-604fa6b881f5@gentoo.org \
--to=arthurzam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=glep@gentoo.org \
--cc=ulm@gentoo.org \
/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