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: Thu, 7 Mar 2024 03:05:46 +0100 [thread overview]
Message-ID: <Zekg-91v4KYQ7go3@debian> (raw)
In-Reply-To: <ZekThJn_-AGkDyRb@dj3ntoo>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hi Oskari, Guillem,
On Wed, Mar 06, 2024 at 07:08:20PM -0600, Oskari Pirhonen wrote:
> They're super helpful for sure. It was really annoying to have to track
> down where some struct was documented if it wasn't in the page I had
> open right then. Now I can just do: man some_struct
Thanks!
BTW, it seems these APIs are not-so-recent to glibc:
$ git blame -- ./time/sys/time.h | grep -e TIMEVAL_TO_TIMESPEC -e TIMESPEC_TO_TIMEVAL
8be918b7bb2 (Ulrich Drepper 2001-01-28 00:00:08 +0000 38) # define TIMEVAL_TO_TIMESPEC(tv, ts) { \
8be918b7bb2 (Ulrich Drepper 2001-01-28 00:00:08 +0000 42) # define TIMESPEC_TO_TIMEVAL(tv, ts) { \
I'm preparing a manual page for them.
Have a loveyl night!
Alex
--
<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 --]
next prev parent reply other threads:[~2024-03-07 2:05 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 [this message]
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
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=Zekg-91v4KYQ7go3@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.