From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
gcc@gcc.gnu.org, libc-alpha@sourceware.org
Subject: Re: [PATCH 0/2] Document void *
Date: Thu, 1 Oct 2020 17:34:47 +0200 [thread overview]
Message-ID: <71c5f264-38f4-18ee-fe96-39aad08c3369@gmail.com> (raw)
In-Reply-To: <20201001150638.102544-1-colomar.6.4.3@gmail.com>
Hello Alex,
On 10/1/20 5:06 PM, Alejandro Colomar wrote:
> Hello Michael,
>
> This type is very special,
> so I will probably have missed some details about it.
I do wonder if we actually need this in page at all, and given:
> Also, do you like the link name?
I really don't like it... I don't want to create files
whose names are globbing characters; that's a road to pain.
So, even if we did document this type in the page,
I don't think we can have a good link name. (I suppose we
could add it to the pagewithout having a link.)
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-10-01 15:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 15:06 [PATCH 0/2] Document void * Alejandro Colomar
2020-10-01 15:06 ` [PATCH 1/2] system_data_types.7: Add 'void *' Alejandro Colomar
2020-10-01 15:06 ` [PATCH 2/2] void-*.3: New link to system_data_types(7) Alejandro Colomar
2020-10-01 15:34 ` Michael Kerrisk (man-pages) [this message]
2020-10-01 15:40 ` [PATCH 0/2] Document void * Alejandro Colomar
2020-10-01 15:49 ` [PATCH v2 0/2] Document 'void *' Alejandro Colomar
2020-10-01 15:49 ` [PATCH v2 1/2] system_data_types.7: Add " Alejandro Colomar
2020-10-01 16:38 ` Michael Kerrisk (man-pages)
2020-10-01 16:55 ` Alejandro Colomar
2020-10-02 11:54 ` Michael Kerrisk (man-pages)
2020-10-08 13:52 ` Vincent Lefevre
2020-10-12 9:36 ` Michael Kerrisk (man-pages)
2020-10-01 17:32 ` Paul Eggert
2020-10-02 8:24 ` Alejandro Colomar
2020-10-02 8:48 ` Alejandro Colomar
2020-10-02 11:44 ` Michael Kerrisk (man-pages)
2020-10-02 9:10 ` David Laight
2020-10-02 17:00 ` Paul Eggert
2020-10-02 10:49 ` Jonathan Wakely
2020-10-02 11:31 ` Michael Kerrisk (man-pages)
2020-10-02 13:06 ` Jonathan Wakely
2020-10-02 13:20 ` Alejandro Colomar
2020-10-02 13:27 ` Jonathan Wakely
2020-10-02 13:51 ` Alejandro Colomar
2020-10-03 8:00 ` Navigational corrections (was: Re: [PATCH v2 1/2] system_data_types.7: Add 'void *') Michael Kerrisk (man-pages)
2020-10-03 9:16 ` Navigational corrections Alejandro Colomar
2020-10-03 11:39 ` Michael Kerrisk (man-pages)
2020-10-05 22:08 ` Alejandro Colomar
2020-10-07 6:53 ` Michael Kerrisk (man-pages)
2020-10-01 15:49 ` [PATCH v2 2/2] void.3: New link to system_data_types(7) Alejandro Colomar
2020-10-02 13:19 ` [PATCH 0/2] Document void * Jonathan Wakely
2020-10-03 11:44 ` Michael Kerrisk (man-pages)
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 12:16 [PATCH 0/2] Document 'void *' 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=71c5f264-38f4-18ee-fe96-39aad08c3369@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.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 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.