From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH RFC libnetfilter_queue 1/1] src: doc: supply missing SYNOPSIS in pktbuff man pages
Date: Sat, 24 Jul 2021 10:56:33 +0200 [thread overview]
Message-ID: <20210724085633.GA21304@salvia> (raw)
In-Reply-To: <YPuN1cuL1ukqzSFl@slk1.local.net>
On Sat, Jul 24, 2021 at 01:49:41PM +1000, Duncan Roe wrote:
> On Thu, Jul 22, 2021 at 07:10:15PM +0200, Pablo Neira Ayuso wrote:
> > The existing autogenerated manpages are still a bit distant to usual
> > Linux Programmer's Manual manpages at quick glance.
>
> I guess doxygen-generated man pages will always be a little bit "distinctive".
>
> Looking carefully, I see a number of doxygen artefacts that can be
> post-processed away.
I mean: If you can achieve this via standard features available in
doxygen to keep this maintainable along time, such as \manonly or
such, then that's good.
Otherwise, extending doxygen should be the way to keep it simple.
I understand doxygen might generate a little but "distintive" output,
that's OK. I'd rather not to add more dependencies on this.
Thanks.
next prev parent reply other threads:[~2021-07-24 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 4:19 [PATCH libmnl 0/1] build: doc: "make" builds & installs a full set of man pages Duncan Roe
2021-06-22 4:19 ` [PATCH libmnl 1/1] " Duncan Roe
2021-06-23 17:26 ` Pablo Neira Ayuso
2021-06-27 4:30 ` Duncan Roe
2021-06-27 4:42 ` Duncan Roe
2021-06-29 9:38 ` Pablo Neira Ayuso
2021-07-02 4:16 ` Duncan Roe
2021-07-07 2:19 ` Duncan Roe
2021-07-17 2:53 ` Duncan Roe
2021-07-17 2:53 ` [PATCH RFC libnetfilter_queue 1/1] src: doc: supply missing SYNOPSIS in pktbuff " Duncan Roe
2021-07-22 17:10 ` Pablo Neira Ayuso
2021-07-24 3:49 ` Duncan Roe
2021-07-24 8:56 ` Pablo Neira Ayuso [this message]
2021-08-09 8:22 ` Duncan Roe
2021-08-09 8:32 ` Duncan Roe
2021-07-17 3:27 ` [PATCH libmnl 1/1] build: doc: "make" builds & installs a full set of " Duncan Roe
2021-07-17 5:47 ` Duncan Roe
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=20210724085633.GA21304@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).