From: Stephen Hemminger <stephen@networkplumber.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
alexhenrie24@gmail.com, branden@debian.org,
linux-man@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] rtnetlink.7: Document struct ifa_cacheinfo
Date: Wed, 6 Nov 2024 09:18:01 -0800 [thread overview]
Message-ID: <20241106091801.3e021842@hermes.local> (raw)
In-Reply-To: <xfzcwmn6syhywvdcu6kn3mkuwqpo5usiwkssblvk6qrpoys5dp@hwgvspb43tdo>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Tue, 5 Nov 2024 12:33:48 +0100
Alejandro Colomar <alx@kernel.org> wrote:
> Hi Alex, Kuniyuki, Branden,
>
> On Mon, Nov 04, 2024 at 09:53:38PM GMT, Kuniyuki Iwashima wrote:
> > From: Alex Henrie <alexhenrie24@gmail.com>
> > Date: Mon, 4 Nov 2024 21:14:20 -0700
> > > struct ifa_cacheinfo contains the address's creation time, update time,
> > > preferred lifetime, and valid lifetime. See
>
> We use two spaces after period (the correct amount). :)
Double spacing after period is a leftover from using typewriters.
Modern usage is single space after period.
https://www.grammarly.com/blog/punctuation-capitalization/spaces-after-period/
These days most contemporary style guides also recommend using a single space between sentences,
including:
The Chicago Manual of Style
The American Psychological Association (often referred to as “APA”)
Microsoft Manual of Style
The Gregg Reference Manual
The Associated Press Stylebook
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-06 17:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 4:14 [PATCH] rtnetlink.7: Document struct ifa_cacheinfo Alex Henrie
2024-11-05 5:53 ` Kuniyuki Iwashima
2024-11-05 11:33 ` Alejandro Colomar
2024-11-06 17:18 ` Stephen Hemminger [this message]
2024-11-06 17:44 ` Alejandro Colomar
2024-11-06 17:48 ` G. Branden Robinson
2024-11-06 17:45 ` G. Branden Robinson
2024-11-06 18:02 ` Alejandro Colomar
2024-11-11 6:17 ` Alex Henrie
2024-11-11 9:34 ` Alejandro Colomar
2024-11-09 16:27 ` Stephen Hemminger
2024-11-11 6:20 ` [PATCH man-pages v2] " Alex Henrie
2024-11-12 1:11 ` Kuniyuki Iwashima
2024-11-12 7:58 ` Alejandro Colomar
2024-11-12 23:26 ` Alejandro Colomar
2024-11-12 23:33 ` Kuniyuki Iwashima
2024-11-12 23:38 ` Alejandro Colomar
2024-11-12 23:46 ` Alejandro Colomar
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=20241106091801.3e021842@hermes.local \
--to=stephen@networkplumber.org \
--cc=alexhenrie24@gmail.com \
--cc=alx@kernel.org \
--cc=branden@debian.org \
--cc=kuniyu@amazon.com \
--cc=linux-man@vger.kernel.org \
--cc=netdev@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).