From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>, pcc@google.com
Cc: mtk.manpages@gmail.com, Dave.Martin@arm.com,
James.Bottomley@hansenpartnership.com, andreyknvl@google.com,
catalin.marinas@arm.com, david.spickett@linaro.org,
deller@gmx.de, ebiederm@xmission.com, eugenis@google.com,
kcc@google.com, kevin.brodsky@arm.com, linux-api@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-man@vger.kernel.org,
oleg@redhat.com, vincenzo.frascino@arm.com, will@kernel.org
Subject: Re: [PATCH] sigaction.2: Document SA_EXPOSE_TAGBITS and the flag support detection protocol
Date: Sun, 15 Nov 2020 10:51:08 +0100 [thread overview]
Message-ID: <44cf5d5c-bd7d-1dab-40e3-0759201a9e34@gmail.com> (raw)
In-Reply-To: <20201114214914.177815-1-colomar.6.4.3@gmail.com>
Hi Alex,
On 11/14/20 10:49 PM, Alejandro Colomar wrote:
> From: Peter Collingbourne <pcc@google.com>
>
> Signed-off-by: Peter Collingbourne <pcc@google.com>
> [alx: srcfix + ffix]
> Cowritten-by: Alejandro Colomar <alx.manpages@gmail.com>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
>
> Hi Michael,
>
> as Peter noted, this patch is not ready
> (code hasn't been merged into the kernel yet).
>
> And a spin-off question:
> How would you prefer it?:
> [
> .B SA_*
> ] (there are 79 similar cases in the pages [1])
> or
> [
> .BR SA_ *
> ] (there are 3 similar cases in the pages [2])
I think the second form has crept in by accident.
The first form is preferred.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-11-15 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 1:41 [PATCH] sigaction.2: Document SA_EXPOSE_TAGBITS and the flag support detection protocol Peter Collingbourne
2020-11-14 21:49 ` Alejandro Colomar
2020-11-15 9:51 ` Michael Kerrisk (man-pages) [this message]
2020-11-16 12:57 ` Dave Martin
2020-11-17 23:52 ` Peter Collingbourne
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=44cf5d5c-bd7d-1dab-40e3-0759201a9e34@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=Dave.Martin@arm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alx.manpages@gmail.com \
--cc=andreyknvl@google.com \
--cc=catalin.marinas@arm.com \
--cc=david.spickett@linaro.org \
--cc=deller@gmx.de \
--cc=ebiederm@xmission.com \
--cc=eugenis@google.com \
--cc=kcc@google.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-man@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pcc@google.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).