Linux Manual Pages development
 help / color / mirror / Atom feed
From: Georg Sauthoff <mail@gms.tf>
To: Alejandro Colomar <alx+linux-man@kernel.org>
Cc: "Alejandro Colomar" <alx@kernel.org>,
	linux-man@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
	"Richard Cochran" <richardcochran@gmail.com>,
	"Nikola Forró" <nforro@redhat.com>,
	"Laurent Georget" <laurent.georget@supelec.fr>,
	"Jeff Epler" <jepler@unpythonic.net>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v1] man/man2/adjtimex.2: Add include, macro and error for clock_adjtime
Date: Sun, 25 Oct 2026 22:37:00 +0100	[thread overview]
Message-ID: <at52fBkoAmohUnC7@framework.lru.li> (raw)
In-Reply-To: <at5M0n93b8Nqjop-@debian>

Hello,

On Sun, Oct 25, 2026 at 07:49:32PM +0100, Alejandro Colomar wrote:
> Hi Georg,
> 
> > Date: 2026-10-25 13:56:56+0100
> > From: Georg Sauthoff <mail@gms.tf>
> > Subject: [PATCH v1] man/man2/adjtimex.2: Add include, macro and error for clock_adjtime
> 
> Please separate this into two patches, each of which does only one
> thing.  The error seems unrelated to the include.

Ok. Yes, it's unrelated. It wasn't my intention to imply that both hunks
are related.

I'll split it and send both as version 2.


> > diff --git a/man/man2/adjtimex.2 b/man/man2/adjtimex.2
> > index f12d9413e..528fd3a6f 100644
> > --- a/man/man2/adjtimex.2
> > +++ b/man/man2/adjtimex.2
> > @@ -17,9 +17,21 @@ .SH SYNOPSIS
> >  .P
> >  .BI "int adjtimex(struct timex *" "buf" );
> >  .P
> > -.BI "int clock_adjtime(clockid_t " clk_id, " struct timex *" "buf" );
> > -.P
> >  .BI "int ntp_adjtime(struct timex *" buf );
> > +.P
> > +.BR #include <time.h>
> 
> BR is for alternating bold and roman, so this seems wrong.  You probably
> want just B (see the include above).

FWIW, I copy and pasted the BR from another man page I picked as
template which already references _GNU_SOURCE, cf.

    $ grep '^\.BR #include' . -r | wc -l
    23

Ok, I change it to B. Also for consistency.


> BTW, I would use
> 
> 	.B #define _GNU_SOURCE
> 	.B #include <time.h>
> 
> and then remove the Feature Test Macro text below.

Ok, no problem. Again, I just copied that style from another man page:

    $ grep '^\.BR feature_test_macros' . -r -A50 | grep '\<_GNU' | wc -l
    62

The define style seems to be more popular, though:

    $ grep '#define _GNU_SOURCE' . -r | wc -l
    153

Plus special space variant:

    $ grep '#define\\~_GNU_SOURCE' . -r | wc -l
    2

I don't really have a preference between these styles and thus follow
your suggestion.

Best regards,
Georg

  reply	other threads:[~2026-10-25 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 12:56 [PATCH v1] man/man2/adjtimex.2: Add include, macro and error for clock_adjtime Georg Sauthoff
2026-10-25 18:49 ` Alejandro Colomar
2026-10-25 21:37   ` Georg Sauthoff [this message]
2026-10-27  0:37 ` [PATCH v2 0/2] man/man2/adjtimex.2: Fix include+add error Georg Sauthoff
2026-10-27  0:37   ` [PATCH v2 1/2] man/man2/adjtimex.2: Add include and macro for clock_adjtime Georg Sauthoff
2026-10-27  0:37   ` [PATCH v2 2/2] man/man2/adjtimex.2: Add error " Georg Sauthoff

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=at52fBkoAmohUnC7@framework.lru.li \
    --to=mail@gms.tf \
    --cc=alx+linux-man@kernel.org \
    --cc=alx@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jepler@unpythonic.net \
    --cc=laurent.georget@supelec.fr \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=nforro@redhat.com \
    --cc=richardcochran@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