From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [PATCH v2 1/3] system_data_types.7: ffix
Date: Mon, 28 Sep 2020 12:34:40 +0200 [thread overview]
Message-ID: <CAKgNAkjOX27k+RFvJC+icZp3dC2bK7aQiTb4Qj4Oc=NfDYZP5w@mail.gmail.com> (raw)
In-Reply-To: <20200928090322.2058-1-colomar.6.4.3@gmail.com>
Hi Alex,
On Mon, 28 Sep 2020 at 11:04, Alejandro Colomar <colomar.6.4.3@gmail.com> wrote:
>
> Normally, text under a section header starts in the next line after the
> header, without a blank line. Follow that pattern.
>
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
>
> Hi Michael,
>
> I had been using .PP because I hadn't seen .br before.
>
> I think .br is the correct format,
> following the pattern in already existing man pages.
I don't disagree with the formatting change, but I am wondering if
there's a better way to do it. I tend to consider (perhaps wrongly)
that the use of .sp and .br is unidiomatic, and over the years I have
replaced a large of them with alternatives. (For example, in many
cases, .sp was being used when .PP should have been.)
If Branden does not tell us of something better, I will just apply
your patch as is.
> BTW, is there any way to copy the CC list with git send-email
> from the email I'm answering to?
> Right now I'm manually copying all of them each time from Thunderbird.
Sorry, I don't know. (Not really an answer to your question,
but are you also aware of "git format-patch --to=... --cc=..." ?)
Thanks,
Michael
next prev parent reply other threads:[~2020-09-28 10:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 21:13 [PATCH 1/3] system_data_types.7: ffix Alejandro Colomar
2020-09-27 21:13 ` [PATCH 2/3] system_data_types.7: Add 'FILE' Alejandro Colomar
2020-09-28 6:04 ` Michael Kerrisk (man-pages)
2020-09-28 9:06 ` [PATCH v2 " Alejandro Colomar
2020-09-29 13:15 ` Alejandro Colomar
2020-09-29 13:35 ` Michael Kerrisk (man-pages)
2020-09-27 21:13 ` [PATCH 3/3] FILE.3: New link to system_data_types(7) Alejandro Colomar
2020-09-28 5:59 ` [PATCH 1/3] system_data_types.7: ffix Michael Kerrisk (man-pages)
2020-09-28 9:03 ` [PATCH v2 " Alejandro Colomar
2020-09-28 10:34 ` Michael Kerrisk (man-pages) [this message]
2020-09-28 10:37 ` Alejandro Colomar
2020-09-28 11:13 ` G. Branden Robinson
2020-09-28 13:06 ` G. Branden Robinson
2020-09-28 13:44 ` Alejandro Colomar
2020-09-30 10:43 ` G. Branden Robinson
2020-09-30 21:32 ` Alejandro Colomar
2020-10-01 7:37 ` Michael Kerrisk (man-pages)
2020-10-01 7:52 ` Alejandro Colomar
2020-10-01 9:36 ` Michael Kerrisk (man-pages)
2020-09-28 10:40 ` [PATCH " G. Branden Robinson
2020-09-28 10:51 ` Alejandro Colomar
2020-09-28 12:49 ` G. Branden Robinson
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='CAKgNAkjOX27k+RFvJC+icZp3dC2bK7aQiTb4Qj4Oc=NfDYZP5w@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=libc-alpha@sourceware.org \
--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;
as well as URLs for NNTP newsgroup(s).