From: Ulrich Mueller <ulm@gentoo.org>
To: Matt Turner <mattst88@gentoo.org>
Cc: Sam James <sam@gentoo.org>,
gentoo-dev@lists.gentoo.org, base-system@gentoo.org,
pr@gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2] 2023-05-08-openssh-configuration-changes: add item
Date: Mon, 08 May 2023 22:49:56 +0200 [thread overview]
Message-ID: <usfc6tuob@gentoo.org> (raw)
In-Reply-To: <CAEdQ38FW_wsRF+iGXJwqUprBHi3bZRMU3756Kfo+aG9SCNf0zA@mail.gmail.com> (Matt Turner's message of "Mon, 8 May 2023 14:13:08 -0400")
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
>>>>> On Mon, 08 May 2023, Matt Turner wrote:
>> > +++ b/2023-05-08-openssh-configuration-changes/2023-05-08-openssh-configuration-changes.en.txt
>>
>> https://www.gentoo.org/glep/glep-0042.html#news-item-identities
>> "This identifier will be in the form yyyy-mm-dd-short-name [...].
>> The short-name is a very short name describing the news item
>> (e.g. yoursql-updates) [...]. While there is no hard restriction on
>> the length of short-name, limiting it to 20 characters is strongly
>> recommended."
> But why? We're not concerned about file system limits, are we?
No, the FS limit will kick in much later.
However, eselect news may truncate identifiers whose short name is
longer than 30 chars, in situations where the identifier is shown to
users (e.g. for removed news items).
So, it's not a hard limit and nothing will really break, but there's
some incentive to keep these names concise.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2023-05-08 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:23 [gentoo-dev] [PATCH v2] 2023-05-08-openssh-configuration-changes: add item Sam James
2023-05-08 17:04 ` Ulrich Mueller
2023-05-08 18:13 ` Matt Turner
2023-05-08 20:49 ` Ulrich Mueller [this message]
2023-05-08 18:28 ` [gentoo-dev] " James Cloos
2023-05-08 18:44 ` Sam James
2023-05-11 1:55 ` Duncan
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=usfc6tuob@gentoo.org \
--to=ulm@gentoo.org \
--cc=base-system@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mattst88@gentoo.org \
--cc=pr@gentoo.org \
--cc=sam@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