From: Mark Brown <broonie@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Laszlo Papp <lpapp@kde.org>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include/linux/regmap.h: fix a couple of typos
Date: Thu, 9 Jan 2014 11:18:50 +0000 [thread overview]
Message-ID: <20140109111850.GF31886@sirena.org.uk> (raw)
In-Reply-To: <52CE0CC8.20500@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Wed, Jan 08, 2014 at 06:43:20PM -0800, Randy Dunlap wrote:
> On 01/08/14 17:46, Laszlo Papp wrote:
> > I still do not get what point you are trying to make. Could you please
> > provide evidence? Because really, this is the usage I have seen in
> > projects out there all around, including the majority of the linux
> > kernel.
> I am used to seeing e.g. and i.e. always followed by a comma when they are
> used to begin a sentence. However, I just checked and some online style
> guides say to omit the comma and some say to use it, and we (Linux kernel)
> don't really have a writing style guide to look at. I think that makes it
> up to the maintainer to decide what is acceptable.
More generally they're just abbreviations for the latin for for example
and that is so (to a reasonable approximation) get used in the same way.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-09 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 17:22 [PATCH] include/linux/regmap.h: fix a couple of typos Laszlo Papp
2014-01-08 18:07 ` Mark Brown
2014-01-08 18:59 ` Laszlo Papp
2014-01-08 19:07 ` Mark Brown
2014-01-08 21:02 ` Laszlo Papp
2014-01-08 21:08 ` Laszlo Papp
2014-01-08 21:49 ` Mark Brown
2014-01-09 1:46 ` Laszlo Papp
2014-01-09 2:43 ` Randy Dunlap
2014-01-09 10:22 ` Laszlo Papp
2014-01-09 12:23 ` Mark Brown
2014-01-09 11:18 ` Mark Brown [this message]
2014-01-08 22:04 ` Randy Dunlap
2014-01-08 19:07 ` Randy Dunlap
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=20140109111850.GF31886@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpapp@kde.org \
--cc=rdunlap@infradead.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