From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Jonas Stein <jstein@gentoo.org>, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Standard parsable format for profiles/package.mask file
Date: Mon, 25 Sep 2023 20:29:16 -0500 [thread overview]
Message-ID: <ZRIz7IH5GIkrXd0g@dj3ntoo> (raw)
In-Reply-To: <w6gfs328nox.fsf@uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Mon, Sep 25, 2023 at 14:03:26 +0200, Ulrich Mueller wrote:
> >>>>> On Sun, 24 Sep 2023, Jonas Stein wrote:
>
> >> # Removal on 2023-10-21. Bug #667687, #667689.
>
> > We should use "after" instead of "on":
>
> > # Removal after T
>
> I wonder if we even need to specify the wording in such detail. For any
> tools parsing the file, it might be enough to say that the line must
> contain, in this order:
>
> - "Removal" (case insensitive?) as the first word,
> - exactly one date in YYYY-MM-DD format,
> - optionally, the word "bug" followed by one or more bug numbers.
>
With the scheme above, the following would be valid (among other more
nonsensical looking things):
# Removal before YYYY-MM-DD. Bug #1, #2
IMO it definitely should require a word with similar meaning to "on" or
"after". How exactly that gets worded in the end, IDK. Maybe it'll end
up as "exactly one of 'on' or 'after'" or something like that.
- Oskari
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-09-26 1:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 19:40 [gentoo-dev] Standard parsable format for profiles/package.mask file Arthur Zamarin
2023-09-21 21:09 ` [gentoo-dev] " Florian Schmaus
2023-09-21 21:36 ` Ulrich Mueller
2023-09-21 21:48 ` Sam James
2023-09-22 6:39 ` Florian Schmaus
2023-09-22 6:53 ` Florian Schmaus
2023-09-22 9:46 ` Ulrich Mueller
2023-09-22 11:51 ` Ulrich Mueller
2023-09-22 14:01 ` Sam James
2023-09-22 14:26 ` Alex Boag-Munroe
2023-09-22 14:36 ` Sam James
2023-09-22 14:50 ` Alex Boag-Munroe
2023-09-22 17:28 ` Arthur Zamarin
2023-09-23 13:59 ` Sam James
2023-09-23 7:02 ` Ulrich Mueller
2023-09-23 13:54 ` Sam James
2023-09-23 14:01 ` Alex Boag-Munroe
2023-09-23 17:48 ` Ulrich Mueller
2023-09-24 18:29 ` Jonas Stein
2023-09-21 21:22 ` [gentoo-dev] " Ulrich Mueller
2023-09-21 22:10 ` Tim Harder
2023-09-21 22:19 ` Sam James
2023-09-22 3:54 ` Oskari Pirhonen
2023-09-22 12:12 ` Arthur Zamarin
2023-09-22 3:59 ` Oskari Pirhonen
2023-09-22 9:21 ` Ulrich Mueller
2023-09-22 9:53 ` Arthur Zamarin
2023-09-22 11:16 ` [gentoo-dev] " Florian Schmaus
2023-09-22 11:23 ` Jaco Kroon
2023-09-24 18:40 ` Jonas Stein
2023-09-25 12:03 ` Ulrich Mueller
2023-09-26 1:29 ` Oskari Pirhonen [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=ZRIz7IH5GIkrXd0g@dj3ntoo \
--to=xxc3ncoredxx@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=jstein@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