public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	g.branden.robinson@gmail.com
Subject: Re: [RFC] memusage.1, uri.7, user-keyring.7, user-session-keyring.7, ld.so.8, tzselect.8: srcfix: Replace \f markup by .
Date: Sun, 15 Nov 2020 21:54:55 +0100	[thread overview]
Message-ID: <accea029-e467-4928-af40-d4cc1bc0be21@gmail.com> (raw)
In-Reply-To: <20201115165256.497403-1-alx.manpages@gmail.com>

Hi Alex,

Briefly...

> And I also found a few weird files (such as zic.8 and zdump.8).
> Where do those come from?
> I'll try to rewrite them using man(7) markup.

Stop!! These pages are special. They are periodically imported from 
the tz project. It's an odd situation. Glibc imports these tools
from the tz project, but does not release manual pages. So,
periodically (when Paul Eggert reminds me), I resync the pages from
the tz project. In general, I try to just leave them alone (although
I have suggested a few fixes upstream to Paul), although I see
I have touched some of those pages in global edits.

> In the meantime,
> I would also have to omit those files from the input to the script.
> Do you have a list of such files?

AFAIR, the only other special page is bpf-helpers.7, which
is generated from the kernel source files using scripts.
Every few months, I try to remember to run the scripts
to resync.

Thanks,

Michael

  reply	other threads:[~2020-11-15 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 16:52 [RFC] memusage.1, uri.7, user-keyring.7, user-session-keyring.7, ld.so.8, tzselect.8: srcfix: Replace \f markup by Alejandro Colomar
2020-11-15 20:54 ` Michael Kerrisk (man-pages) [this message]
2020-11-16  0:33   ` Alejandro Colomar (man-pages)
2020-11-16 10:36     ` Michael Kerrisk (man-pages)
2020-11-16  8:26   ` Michael Kerrisk (man-pages)

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=accea029-e467-4928-af40-d4cc1bc0be21@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --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