From: shaheed <srhaque@iee.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: ms@citd.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel source spellchecker
Date: Sat, 1 Mar 2003 18:01:19 +0000 [thread overview]
Message-ID: <200303011801.19219.srhaque@iee.org> (raw)
In-Reply-To: <20030301163555.GA1379@wohnheim.fh-wedel.de>
On Saturday 01 Mar 2003 4:35 pm, Jörn Engel wrote:
> On Sat, 1 March 2003 15:57:13 +0000, shaheed wrote:
...
> >
> > brain-damaged=dain-bramaged,dain bramaged
>
> What's wrong with those? Yes, they don't exist in a dictionary, but
> neither do a
...
> I don't know where art starts and whether kernel documentation is a
> decent place for it, but a second thought might be worth it. :)
Hi Jörn,
Like you, I do get the joke: but in this case as in others, I took the view
that the needs of those whose first language was not English should prevail.
(Yes, I also know about the convention that the kernel is defined to be in
English.)
And, being not yet of even janitor status (:-)) myself, I did not submit the
patch: I guess whoever does that has the final call!
Cheers, Shaheed
next prev parent reply other threads:[~2003-03-01 17:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 15:57 [PATCH] kernel source spellchecker shaheed
2003-03-01 16:35 ` Jörn Engel
2003-03-01 18:01 ` shaheed [this message]
2003-03-01 18:31 ` Jörn Engel
2003-03-05 18:10 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-03-02 18:56 Jared Daniel J. Smith
2003-03-02 17:22 ` Bernd Petrovitsch
2003-03-02 17:47 ` Werner Almesberger
2003-03-02 18:28 ` Bernd Petrovitsch
2003-03-02 18:46 ` Steven Cole
2003-03-02 22:32 ` Alan Cox
[not found] <20030301160017$56fc@gated-at.bofh.it>
2003-03-01 18:39 ` Pascal Schmidt
2003-02-27 6:59 Dan Kegel
[not found] ` <1046330232.15763.97.camel@localhost.localdomain>
2003-03-01 5:38 ` Dan Kegel
2003-03-01 14:11 ` Matthias Schniedermeyer
2003-03-01 17:13 ` Matthias Schniedermeyer
2003-03-01 18:54 ` Dan Kegel
2003-03-01 19:18 ` Steven Cole
2003-03-01 21:20 ` Dan Kegel
2003-03-02 3:45 ` jw schultz
2003-03-02 2:08 ` Dan Kegel
2003-03-02 3:02 ` Dan Kegel
2003-03-02 3:54 ` Steven Cole
2003-03-02 8:04 ` Dan Kegel
2003-03-02 4:16 ` Steven Cole
2003-03-02 8:21 ` Dan Kegel
2003-03-02 8:40 ` jw schultz
2003-03-02 11:21 ` David Woodhouse
2003-03-02 13:49 ` Steven Cole
2003-03-02 14:55 ` David Woodhouse
2003-03-02 22:44 ` Alan Cox
2003-03-02 22:59 ` John Bradford
2003-03-03 2:29 ` Dan Kegel
[not found] ` <3E62C0FF.1090700@kegel.com>
[not found] ` <1046661777.7527.518.camel@spc1.mesatop.com>
2003-03-03 5:36 ` Dan Kegel
[not found] ` <3E62E4C0.9070103@kegel.com>
[not found] ` <1046668274.7527.533.camel@spc1.mesatop.com>
2003-03-03 5:48 ` Dan Kegel
2003-03-02 15:35 ` Dan Kegel
2003-03-02 8:09 ` Matthias Schniedermeyer
2003-03-02 8:13 ` Matthias Schniedermeyer
2003-03-02 3:29 ` Steven Cole
2003-03-01 19:30 ` Matthias Schniedermeyer
2003-03-01 20:33 ` Matthias Schniedermeyer
2003-03-01 21:25 ` Dan Kegel
2003-03-01 21:25 ` Matthias Schniedermeyer
2003-03-02 9:15 ` John Bradford
2003-03-02 9:31 ` Matthias Schniedermeyer
2003-03-02 3:16 ` Horst von Brand
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=200303011801.19219.srhaque@iee.org \
--to=srhaque@iee.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
/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