linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk@jwilk.net>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, <linux-man@vger.kernel.org>
Subject: Re: [PATCH 1/2] system_data_types.7: srcfix
Date: Fri, 19 Aug 2022 20:03:23 +0200	[thread overview]
Message-ID: <20220819180323.dbsgxh5qvcjabjm6@jwilk.net> (raw)
In-Reply-To: <20200930101213.2m2pt3jrspvcrxfx@localhost.localdomain>

* G. Branden Robinson <g.branden.robinson@gmail.com>, 2020-09-30 20:12:
>+\(bu Do I ever need to use an empty macro argument ("")?
>+Probably not.

FWIW, man-pages(7) says it's OK to use empty string for the 4th 
argument of .TH:

"For library calls that are part of glibc or one of the other common GNU 
libraries, just use GNU C Library, GNU, or an empty string."

There used to be a lot of such .TH calls; now there's only a few left:

$ grep -r '[.]TH .*""' man*/
man7/posixoptions.7:.TH POSIXOPTIONS 7 2021-08-27 "" "Linux Programmer's Manual"
man7/bpf-helpers.7:.TH BPF-HELPERS 7 "" "" ""
man8/zdump.8:.TH ZDUMP 8 2020-04-27 "" "Linux System Administration"
man8/zic.8:.TH ZIC 8 2020-08-13 "" "Linux System Administration"

-- 
Jakub Wilk

  reply	other threads:[~2022-08-19 19:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  8:03 [PATCH 1/2] system_data_types.7: srcfix Alejandro Colomar
2020-09-25  8:03 ` [PATCH 2/2] " Alejandro Colomar
2020-09-25 10:40   ` Michael Kerrisk (man-pages)
2020-09-25 11:28     ` [PATCH v2 " Alejandro Colomar
2020-09-25 12:02       ` Michael Kerrisk (man-pages)
2020-09-25 12:46         ` Alejandro Colomar
2020-09-25 10:39 ` [PATCH 1/2] " Michael Kerrisk (man-pages)
2020-09-27  6:10 ` G. Branden Robinson
2020-09-27 20:24   ` Alejandro Colomar
2020-09-28 12:58     ` G. Branden Robinson
2020-09-28 13:29   ` Jakub Wilk
2020-09-28 13:40     ` G. Branden Robinson
2020-09-29 12:13     ` Michael Kerrisk (man-pages)
2020-09-30 10:12       ` G. Branden Robinson
2022-08-19 18:03         ` Jakub Wilk [this message]
2022-08-19 23:53           ` Alejandro Colomar
2022-08-20  5:43           ` G. Branden Robinson
2022-08-20 11:57             ` .TH 4th field (Was: [PATCH 1/2] system_data_types.7: srcfix) Alejandro Colomar
2022-08-20 12:20               ` G. Branden Robinson
2022-08-20 12:40                 ` Alejandro Colomar
2022-08-20 13:04                   ` Alejandro Colomar
2022-08-21 11:46                   ` Alejandro Colomar
2022-08-24 13:22                   ` Ingo Schwarze
2022-08-24 15:04                     ` Alejandro Colomar
2022-08-24 17:12                       ` Ingo Schwarze
2022-08-24 19:37                         ` 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=20220819180323.dbsgxh5qvcjabjm6@jwilk.net \
    --to=jwilk@jwilk.net \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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;
as well as URLs for NNTP newsgroup(s).