From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Rationale for .PD 0 in old commit
Date: Thu, 12 Nov 2020 23:26:16 +0100 [thread overview]
Message-ID: <6b34f96a-7930-3338-e286-c17fad67b5e3@gmail.com> (raw)
Hello Michael,
I'd like to know, if you happen to remember it,
the rationale for using [.PD 0] + [.RS] + [.TP 24]
in perf_event_open.2.
It was added in commit 2b538c3e5380cbe81a5c053cd183788e3a13f0cb.
I guess it's related to the fact that
there are too many levels of indentation,
but is it really needed?
I think everything fits correctly in an 80-column terminal
without needing that workaround.
Is it maybe for other than terminals?
May I remove those in my attempt to simplify and standardize the markup?
Thanks,
Alex
next reply other threads:[~2020-11-12 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 22:26 Alejandro Colomar (man-pages) [this message]
2020-11-12 22:30 ` Rationale for .PD 0 in old commit Alejandro Colomar (man-pages)
2020-11-13 7:17 ` 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=6b34f96a-7930-3338-e286-c17fad67b5e3@gmail.com \
--to=alx.manpages@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