From: Rick Jones <rick.jones2@hp.com>
To: davids@webmaster.com
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] Stop scaring users with "treason uncloaked!"
Date: Thu, 18 Dec 2008 16:58:56 -0800 [thread overview]
Message-ID: <494AF1D0.8060400@hp.com> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKKEJJBPAD.davids@webmaster.com>
David Schwartz wrote:
>>Most people won't actually think their printer is on fire. But most
>>people WILL think there is serious cause for concern when they see this
>>for the first time in dmesg. Many will search the net for explanations
>>and come away confused and not entirely reassured. And at least one
>>clueless guy will call the police because he still thinks he's under
>>attack.
>
>
> Messages about something or other being "illegal" occur about 345 times in
> the Linux kernel source code. Are we going to start patching those too?
>
> We have "illegal norm", "illegal input", "illegal call", "illegal type",
> "illegal bits", "illegal root port number", "illegal host number", "illegal
> DMA data", "illegal dimensions" (who do you call about that one?), "illegal
> phase", "illegal page number", "illegal seek", and on, and on, and on.
>
> I suspect that if I submitted a patch to change all of those to "invalid",
> I'd be considered a kook. (Well, more of a kook, anyway.)
All issues of your kookiness aside :) I suspect that the continuing
spread of "linux" among the masses will mean a need for greater care in
message wording. Whether that means that "illegal <foo>" needs to be
changed I cannot say, but if it does it shouldn't come as a surprise.
rick jones
next prev parent reply other threads:[~2008-12-19 0:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 22:16 [PATCH] Stop scaring users with "treason uncloaked!" Matt Mackall
2008-12-18 22:33 ` Ilpo Järvinen
2008-12-18 22:36 ` Herbert Xu
2008-12-18 23:50 ` Matt Mackall
2008-12-19 0:15 ` David Miller
2008-12-19 3:49 ` Matt Mackall
2008-12-19 3:54 ` David Miller
2008-12-19 18:13 ` markus reichelt
2008-12-19 0:08 ` David Miller
2008-12-18 22:44 ` Herbert Xu
2008-12-18 22:49 ` Alan Cox
2008-12-18 23:02 ` Herbert Xu
2008-12-18 23:14 ` Alan Cox
2008-12-19 0:07 ` David Miller
2008-12-18 23:06 ` Matt Mackall
2008-12-19 0:45 ` David Schwartz
2008-12-19 0:55 ` Krzysztof Halasa
2008-12-19 0:58 ` Rick Jones [this message]
2009-01-26 17:46 ` Lennart Sorensen
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=494AF1D0.8060400@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=davids@webmaster.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@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 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.