From: "Michael Kerrisk \(man-pages\) via Libc-alpha" <libc-alpha@sourceware.org>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>,
Hans Petter Selasky <hps@selasky.org>
Cc: linux-man <linux-man@vger.kernel.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
mtk.manpages@gmail.com
Subject: Re: queue.3 overhaul
Date: Wed, 21 Oct 2020 06:53:56 +0200 [thread overview]
Message-ID: <d9b8f226-2972-d238-ff7a-0298104e07e9@gmail.com> (raw)
In-Reply-To: <213d9db0-ebf5-ddcc-c796-2478143db9c9@gmail.com>
On 10/20/20 1:42 PM, Alejandro Colomar wrote:
>
>
> On 2020-10-20 13:22, Hans Petter Selasky wrote:
>> Hi,
>>
>> You may want to import new queue macros from FreeBSD, especially for C++
>> use.
>>
>> https://svnweb.freebsd.org/base/head/sys/sys/queue.h
>>
>> https://svnweb.freebsd.org/base?view=revision&revision=284915
>>
>> --HPS
>
>
> Hi Hans,
>
> Thanks for the suggestion.
>
> I'll add the documentation to the manual pages commented out
> (as with other queue.h macros that aren't present on glibc),
> and if glibc adds them in the future,
> it can then be uncommented.
Thanks for that, Alex. (And thanks for the heads-up, Hans.)
Cheers,
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-21 4:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 15:29 queue.3 overhaul Alejandro Colomar via Libc-alpha
2020-10-20 4:08 ` Michael Kerrisk (man-pages) via Libc-alpha
2020-10-20 10:36 ` Alejandro Colomar via Libc-alpha
2020-10-20 11:22 ` Hans Petter Selasky
2020-10-20 11:42 ` Alejandro Colomar via Libc-alpha
2020-10-21 4:53 ` Michael Kerrisk (man-pages) via Libc-alpha [this message]
2020-10-23 9:50 ` sys/queue.h: Add macros present on BSDs Alejandro Colomar via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d9b8f226-2972-d238-ff7a-0298104e07e9@gmail.com \
--to=libc-alpha@sourceware.org \
--cc=colomar.6.4.3@gmail.com \
--cc=hps@selasky.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).