From: Alejandro Colomar <alx@kernel.org>
To: Guillem Jover <guillem@hadrons.org>, linux-man@vger.kernel.org
Subject: Re: Order priority issues for special 3type sub-section
Date: Wed, 20 Mar 2024 11:07:27 +0100 [thread overview]
Message-ID: <Zfq1X2Fj_uqzfLqu@debian> (raw)
In-Reply-To: <Zfqp50nfXipmM4dA@thunder.hadrons.org>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On Wed, Mar 20, 2024 at 10:18:31AM +0100, Guillem Jover wrote:
> Hi!
Hi Guillem!
> On Thu, 2024-03-07 at 05:06:29 +0100, Guillem Jover wrote:
> > In this particular case, what I'll be doing is to remove the
> > timeval(3bsd), timespec(3bsd) links everywhere, and stop installing
> > the TIMEVAL_TO_TIMESPEC(3bsd) and TIMESPEC_TO_TIMEVAL(3bsd) on glibc
> > based systems, and check on what others these are already provided,
> > and install those there conditionally.
>
> This has been done now as part of the libbsd 0.12.2 release.
Thanks! I saw it when checking the err.h link pages stuff.
I thought of CCing you about the man-pages-6.7 release. :)
Have a lovely Spring!
Alex
> Thanks,
> Guillem
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-20 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 23:22 Order priority issues for special 3type sub-section Guillem Jover
2024-03-07 0:42 ` Alejandro Colomar
2024-03-07 1:08 ` Oskari Pirhonen
2024-03-07 2:05 ` Alejandro Colomar
2024-03-07 2:09 ` Mail-Followup-To header (was: Order priority issues for special 3type sub-section) Alejandro Colomar
2024-03-07 9:37 ` Lennart Jablonka
2024-03-07 10:37 ` Alejandro Colomar
2024-03-07 4:06 ` Order priority issues for special 3type sub-section Guillem Jover
2024-03-07 10:24 ` Alejandro Colomar
2024-03-20 9:18 ` Guillem Jover
2024-03-20 10:07 ` Alejandro Colomar [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=Zfq1X2Fj_uqzfLqu@debian \
--to=alx@kernel.org \
--cc=guillem@hadrons.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.