From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
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 11:48:04 -0600 [thread overview]
Message-ID: <20241106174804.lmgi4zuypwb2ktcq@illithid> (raw)
In-Reply-To: <soyssk73kxv4njvwmfq635q4wolfjhgprlq3mfvxnciurzxhsh@g72tril7ys2k>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
At 2024-11-06T18:44:08+0100, Alejandro Colomar wrote:
> Paraphrasing the Linux kernel coding style...
>
> First off, I’d suggest printing out a copy of the Chicago Manual
> of Style, and NOT read it. Burn it, it’s a great symbolic
> gesture.
I wouldn't go that far. CMoS has much that is valuable.
Russell Harper is simply not a reliable source regarding the
inter-sentence spacing issue. As we've seen, he has a lot of company.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-06 17:48 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
2024-11-06 17:44 ` Alejandro Colomar
2024-11-06 17:48 ` G. Branden Robinson [this message]
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=20241106174804.lmgi4zuypwb2ktcq@illithid \
--to=g.branden.robinson@gmail.com \
--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 \
--cc=stephen@networkplumber.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 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.