From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: mtk.manpages@gmail.com, lkml <linux-kernel@vger.kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>,
keyrings@vger.kernel.org, linux-man <linux-man@vger.kernel.org>
Subject: Re: Revised keyrings(7) man page for review
Date: Tue, 13 Dec 2016 14:41:35 +0100 [thread overview]
Message-ID: <0fb87812-56f9-df39-ef74-78d30cfaaeb8@gmail.com> (raw)
In-Reply-To: <26757.1481635886@warthog.procyon.org.uk>
Hi David,
On 12/13/2016 02:31 PM, David Howells wrote:
> Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
>
>> I use/Linux man-pages uses the "Oxford comma" convention.
>
> "... an optional comma ..." ;-)
>
> There's also:
>
> ... LSM security checks are still performed, and may filter out
> further keys that the process is not authorized to view.
>
> but has two parts and isn't a list... ;-P
Oxford comma doesn't apply there... But, to me, it depends how
you read the text aloud. I'd read it with a pause where the comma is,
and so added a comma there.
>
>>>> D The key is dead (i.e., has been deleted). (A
>>>> key may be briefly in this state during
>>>> garbage collection.)
>>>
>>> No - "dead" in this context means that the key type was unregistered.
>>
>> Okay, so the text should read as:
>>
>> D The key is dead (i.e., the key has been unregis‐
>> tered). (A key may be briefly in this state
>> during garbage collection.)
>>
>> Right?
>
> Not quite. The driver for the key type has been unregistered, not the key.
Bother. I meant to write "key type"! Fixed.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2016-12-13 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 15:47 Michael Kerrisk
2016-11-26 12:51 ` Michael Kerrisk (man-pages)
2016-12-13 11:35 ` David Howells
2016-12-13 12:43 ` Michael Kerrisk (man-pages)
2016-12-13 12:57 ` Michael Kerrisk (man-pages)
2016-12-13 13:38 ` David Howells
2016-12-13 13:52 ` Michael Kerrisk (man-pages)
2016-12-13 14:20 ` David Howells
2016-12-14 7:27 ` Michael Kerrisk (man-pages)
2016-12-13 13:31 ` David Howells
2016-12-13 13:41 ` Michael Kerrisk (man-pages) [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=0fb87812-56f9-df39-ef74-78d30cfaaeb8@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=dhowells@redhat.com \
--cc=evgsyr@gmail.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.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
all inboxes | Powered by JetHome®