From: "Alejandro Colomar (man-pages)" <firstname.lastname@example.org>
To: Greg Banks <email@example.com>
Cc: Michael Kerrisk <firstname.lastname@example.org>,
DJ Delorie <email@example.com>,
"G. Branden Robinson" <firstname.lastname@example.org>
Subject: Re: [patch] nscd.conf.5: describe reloading, clarifications
Date: Thu, 5 Aug 2021 08:58:33 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
CC += Branden
On 8/4/21 3:40 PM, Greg Banks wrote:
> Hi Alejandro,
> > Could you please use the same method you used for sending v1 to send
> an v3? \
> I did but apparently the email stack at my end insists on adding some
> randomness to its behavior. I'm going to try and step outside this
> email text damage drama and send a pull request separately.
Hmm, not good.
The worst part is that as your emails are not plain text, they don't
reach the mailing list (only the first one did). If you can't solve it
(I suggest using git-send-email(1), to avoid that randomness), I suggest
that you send the email anyway as good as you can (better send it both
inline and as an attachment, so that it is more likely that one of them
will apply), and if it applies to my tree, I'll apply it and also
forward it to the list as plain text.
>> Also, please see some comments below.
> Applied, thanks.
>> >> +.PP
>> That's not correct. Did you copy that from another place? If so,
>> please tell me because I should fix it.
> No, it's a habit left over from the last time I contributed to this
> project (in 2008). It seems the rules have changed.
>> We use that between paragraphs, but not before the first one nor after
>> the last one.
> Ok, sure, but in that case the description of .PP in man(7) is wrong
> .PP Begin a new paragraph and reset prevailing indent.
That's something that I had pending to address from Branden. That page
is a mix of things that should go into man-pages(7), groff_man_style(7),
and groff_man(7), and then man(7) should be removed and replaced by a
link page to groff_man(7).
You can read groff_man(7) (provided by the groff package), which tells
us that .SH already does what .PP does (start a clean paragraph) (and it
does more things, of course). The thing is that if you add .PP after
.SH you will have a blank line (and this an exercise of my mental groff,
which I hope doesn't fail me this time), and it would be a bit weird to
have a blank line after the section title.
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
next prev parent reply other threads:[~2021-08-05 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 22:09 [patch] nscd.conf.5: describe reloading, clarifications Greg Banks
2021-07-28 20:31 ` Alejandro Colomar (man-pages)
2021-07-29 11:55 ` nonbreaking spaces (was: [patch] nscd.conf.5: describe reloading, clarifications) G. Branden Robinson
2021-07-29 12:18 ` Alejandro Colomar (man-pages)
2021-07-29 13:58 ` G. Branden Robinson
2021-07-29 14:22 ` Alejandro Colomar (man-pages)
[not found] ` <BL0PR2101MB1316FA480EE808D34FA523EEA1F09@BL0PR2101MB1316.namprd21.prod.outlook.com>
2021-08-03 8:08 ` [patch] nscd.conf.5: describe reloading, clarifications Alejandro Colomar (man-pages)
[not found] ` <BL0PR2101MB13161815183CB7E6F5D8E61EA1F09@BL0PR2101MB1316.namprd21.prod.outlook.com>
2021-08-04 7:43 ` Alejandro Colomar (man-pages)
[not found] ` <BL0PR2101MB13161650B82F826B74E5DBD0A1F19@BL0PR2101MB1316.namprd21.prod.outlook.com>
2021-08-05 6:58 ` Alejandro Colomar (man-pages) [this message]
2021-08-05 7:38 ` G. Branden Robinson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.