From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Standard parsable format for profiles/package.mask file
Date: Fri, 22 Sep 2023 13:16:39 +0200 [thread overview]
Message-ID: <645f542c-38b3-ddf1-7c0d-1a4fe32d12e3@gentoo.org> (raw)
In-Reply-To: <b2a2515f-8c1e-4422-8cec-cd4fe3a4727c@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 673 bytes --]
On 21/09/2023 21.40, Arthur Zamarin wrote:
> If this is a last-rite message, the last line must list the last-rite
> last date (removal date) and the last-rite bug number. You can also list
FWIW, I would assume the last-rite date to be the date where the
package's last rites where initiated, i.e., where it was p.masked. The
removal date would be the date on which the packages was cleaned from
the tree.
> other bugs relevant to the last-rite. So I think a format of: "Removal
> on ${REMOVAL_DATE}.
I now we, myself included, often wrote "Removal on…", however, I wonder
if we should reflect reality and write "Removal after…" instead.
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17273 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2023-09-22 11:17 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 ` Florian Schmaus [this message]
2023-09-22 11:23 ` [gentoo-dev] " Jaco Kroon
2023-09-24 18:40 ` Jonas Stein
2023-09-25 12:03 ` Ulrich Mueller
2023-09-26 1:29 ` Oskari Pirhonen
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=645f542c-38b3-ddf1-7c0d-1a4fe32d12e3@gentoo.org \
--to=flow@gentoo.org \
--cc=gentoo-dev@lists.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