From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH 4/9] sigevent.3: New link to new documented type in system_data_types(7)
Date: Fri, 18 Sep 2020 23:39:16 +0200 [thread overview]
Message-ID: <3f33a784-6771-d91f-ae15-2ba599c108ea@gmail.com> (raw)
In-Reply-To: <8cea2a6b-bbe1-3289-a0c2-3baa75ec757a@gmail.com>
Hi Michael,
On 2020-09-18 23:10, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
>
> On 9/18/20 7:04 PM, Alejandro Colomar wrote:
>> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
>> ---
>> man3/sigevent.3 | 1 +
>> 1 file changed, 1 insertion(+)
>> create mode 100644 man3/sigevent.3
>
> I think that I won't apply this, since it will hide sigevent(7).
> Okay?
>
> Thanks,
>
> Michael
>
>
>>
>> diff --git a/man3/sigevent.3 b/man3/sigevent.3
>> new file mode 100644
>> index 000000000..db50c0f09
>> --- /dev/null
>> +++ b/man3/sigevent.3
>> @@ -0,0 +1 @@
>> +.so man7/system_data_types.7
>>
>
>
Fine, sigevent(7) already documents the type, so it's perfect. The
type will be documented in system_data_types.7 anyway, so no problem.
I guess you'll add a reference to system_data_types(7) in sigevent(7),
right?
Thanks,
Alex
next prev parent reply other threads:[~2020-09-18 21:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 17:04 [PATCH 0/9] Document aiocb, sigevent, siginfo_t Alejandro Colomar
2020-09-18 17:04 ` [PATCH 1/9] system_data_types.7: ffix Alejandro Colomar
2020-09-18 20:49 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 2/9] system_data_types.7: srcfix: Add FIXME note: Add descriptions Alejandro Colomar
2020-09-18 20:50 ` Michael Kerrisk (man-pages)
2020-09-18 21:03 ` Michael Kerrisk (man-pages)
2020-09-18 21:35 ` Alejandro Colomar
2020-09-18 17:04 ` [PATCH 3/9] system_data_types.7: Document sigevent Alejandro Colomar
2020-09-18 21:09 ` Michael Kerrisk (man-pages)
2020-09-18 21:36 ` Alejandro Colomar
2020-09-18 17:04 ` [PATCH 4/9] sigevent.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-18 21:10 ` Michael Kerrisk (man-pages)
2020-09-18 21:39 ` Alejandro Colomar [this message]
2020-09-18 21:43 ` Michael Kerrisk (man-pages)
2020-09-18 21:57 ` Alejandro Colomar
2020-09-19 8:11 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 5/9] system_data_types.7: srcfix: cosmetic: Visually sparate types Alejandro Colomar
2020-09-18 21:14 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 6/9] system_data_types.7: Document aiocb Alejandro Colomar
2020-09-18 17:04 ` [PATCH 7/9] aiocb.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-18 21:28 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH 8/9] system_data_types.7: Document siginfo_t Alejandro Colomar
2020-09-18 21:42 ` Michael Kerrisk (man-pages)
2020-09-18 21:45 ` Alejandro Colomar
2020-09-20 18:05 ` [PATCH v2 " Alejandro Colomar
2020-09-20 20:19 ` Michael Kerrisk (man-pages)
2020-09-20 18:05 ` [PATCH v2 9/9] siginfo_t.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-20 20:19 ` Michael Kerrisk (man-pages)
2020-09-18 17:04 ` [PATCH " Alejandro Colomar
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=3f33a784-6771-d91f-ae15-2ba599c108ea@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.