From: Alejandro Colomar <alx.manpages@gmail.com>
To: Sam James <sam@gentoo.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2 2/2] feature_test_macros.7: document _TIME_BITS
Date: Thu, 13 Oct 2022 21:19:31 +0200 [thread overview]
Message-ID: <bba53c12-bf59-e9f1-4649-14644904801f@gmail.com> (raw)
In-Reply-To: <1C02DD4E-3F55-4D7D-9D95-02B01F68A890@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 935 bytes --]
On 10/13/22 20:52, Sam James wrote:
>>
>> Please use semantic newlines. See man-pages(7):
>>
>> Use semantic newlines
>> In the source of a manual page, new sentences should be
>> started on new lines, long sentences should be split into
>> lines at clause breaks (commas, semicolons, colons, and
>> so on), and long clauses should be split at phrase bound‐
>> aries. This convention, sometimes known as "semantic
>> newlines", makes it easier to see the effect of patches,
>> which often operate at the level of individual sentences,
>> clauses, or phrases.
>>
>
> Mea culpa -- let me read that over again :)
If you're curious, here you'll find a bit more about it:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit?id=6ff6f43d68164f99a8c3fb66f4525d145571310c>
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-13 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:30 [PATCH v2 1/2] time_t.3type: reference _TIME_BITS Sam James
2022-10-13 18:30 ` [PATCH v2 2/2] feature_test_macros.7: document _TIME_BITS Sam James
2022-10-13 18:47 ` Alejandro Colomar
2022-10-13 18:52 ` Sam James
2022-10-13 19:17 ` Alejandro Colomar
2022-10-13 20:57 ` Sam James
2022-10-13 19:19 ` Alejandro Colomar [this message]
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=bba53c12-bf59-e9f1-4649-14644904801f@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=sam@gentoo.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