From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Issue in man page cgroup_namespaces.7
Date: Sun, 4 Dec 2022 22:22:10 +0100 [thread overview]
Message-ID: <9016dd33-687b-5461-0f2f-10318ca4ed81@gmail.com> (raw)
In-Reply-To: <20221204201107.GE15305@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
Hi Helge,
On 12/4/22 21:11, Helge Kreutzmann wrote:
> Hello Alejandro,
> On Sun, Dec 04, 2022 at 09:07:45PM +0100, Alejandro Colomar wrote:
>> On 12/4/22 10:07, Helge Kreutzmann wrote:
>>> Without further ado, the following was found:
>>>
>>> Issue: user ID → UID
>>
>> IMO, (and I believe Branden will agree), user ID is more informative than
>> UID. If any change, I'd apply some consistency in the other direction (don't
>> know how much inconsistent the pages are regarding that): UID -> user ID.
>>
>> So, WONTFIX. Thanks for the reports!
>
> Noted.
>
> However, you might consider making the link once, i.e. on first
> occurence do
> user ID → user ID (UID)
>
Yep, I'll do that. Thanks!
Cheers,
Alex
> Greetings
>
> Helge
>
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-04 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 9:07 Issue in man page cgroup_namespaces.7 Helge Kreutzmann
2022-12-04 20:07 ` Alejandro Colomar
2022-12-04 20:11 ` Helge Kreutzmann
2022-12-04 21:22 ` Alejandro Colomar [this message]
2022-12-05 13:14 ` Jakub Wilk
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-09-01 13:39 ` Alejandro Colomar
2022-03-13 12:34 Helge Kreutzmann
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=9016dd33-687b-5461-0f2f-10318ca4ed81@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
/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