From: Tomas Szepe <szepe@pinerecords.com>
To: Michael Hayes <mike@aiinc.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Spelling in 2.6.2
Date: Wed, 11 Feb 2004 19:02:33 +0100 [thread overview]
Message-ID: <20040211180233.GC31676@louise.pinerecords.com> (raw)
In-Reply-To: <200402102009.i1AK91T20554@aiinc.aiinc.ca>
On Feb-10 2004, Tue, 12:09 -0800
Michael Hayes <mike@aiinc.ca> wrote:
> I was curious how fast spelling errors flow into the kernel, so I
> looked at the + lines in the 2.6.2 patch. A few of the errors
> already existed, but most of them are new. It turns out that there
> are around 200 new spelling errors in 2.6.2.
Must be because today's keyboards are shite. ;)
-TS
next prev parent reply other threads:[~2004-02-11 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 20:09 Spelling in 2.6.2 Michael Hayes
2004-02-10 20:54 ` DervishD
2004-02-11 1:19 ` Randy.Dunlap
2004-02-11 11:06 ` Geert Uytterhoeven
2004-02-11 9:36 ` vda
2004-02-11 12:43 ` Printk message and numbers formating - was " Michael Frank
2004-02-11 18:02 ` Tomas Szepe [this message]
2004-02-14 0:46 ` Pavel Machek
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=20040211180233.GC31676@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@aiinc.ca \
/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