From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Guillem Jover <guillem@hadrons.org>, linux-man@vger.kernel.org
Subject: Re: Order priority issues for special 3type sub-section
Date: Wed, 6 Mar 2024 19:08:20 -0600 [thread overview]
Message-ID: <ZekThJn_-AGkDyRb@dj3ntoo> (raw)
In-Reply-To: <ZekNZuR3nRczAIqX@debian>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
On Thu, Mar 07, 2024 at 01:42:14 +0100, Alejandro Colomar wrote:
> Hi Guillem!
>
> On Thu, Mar 07, 2024 at 12:22:58AM +0100, Guillem Jover wrote:
> >
> > (BTW, I very much like that these types are provided on their own
> > manual pages, and their own sub-section, thanks for that!)
>
> Thanks!! I had to fight a bit for them. It's good to read positive
> feedback. :)
>
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
- Oskari
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-07 1:08 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 [this message]
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
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=ZekThJn_-AGkDyRb@dj3ntoo \
--to=xxc3ncoredxx@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox