public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Arthur Zamarin <arthurzam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org,  glep@gentoo.org
Subject: Re: [gentoo-dev] [DRAFT] GLEP 84: Standard format for package.mask files
Date: Thu, 05 Oct 2023 21:36:49 +0200	[thread overview]
Message-ID: <ua5swyi7i@gentoo.org> (raw)
In-Reply-To: <bbb736b0-ea6e-41e9-8ddb-e6bdefb485de@gentoo.org> (Arthur Zamarin's message of "Thu, 5 Oct 2023 21:49:48 +0300")

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

>>>>> On Thu, 05 Oct 2023, Arthur Zamarin wrote:

> On 05/10/2023 06.12, Michał Górny wrote:
>> This is inconsistent with the current usage, and confusing.  "After"
>> makes it unclear whether the list is inclusive (i.e. "remove on that day
>> or later") or exclusive ("remove the next day or later"),
>> and in the latter case it's quite backwards.

> Hmm, I don't really care what word we use here, but I do want us to
> agree on one word (cause I'll need to update `pkgdev mask`). Some of the
> considerations against "on" (currently used) is the fact: does it mean
> it isn't fine to remove after it?
> Does English has a nice word for ">= time"?

Make it "on", because the date specified is the intended removal date
when the entry is added.

That is, users cannot rely on the package still being present at any
later date.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  reply	other threads:[~2023-10-05 19:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 18:43 [gentoo-dev] [DRAFT] GLEP 84: Standard format for package.mask files Arthur Zamarin
2023-10-05  3:12 ` Michał Górny
2023-10-05 18:49   ` Arthur Zamarin
2023-10-05 19:36     ` Ulrich Mueller [this message]
2023-10-05 19:31   ` Arthur Zamarin
2023-10-05 19:44   ` Ulrich Mueller
2023-10-05 18:40 ` [gentoo-dev] " Ulrich Mueller
2023-10-05 19:19   ` Arthur Zamarin

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=ua5swyi7i@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=glep@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