From: rct@gherkin.frus.com (Bob_Tracy)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The tainted message
Date: Sat, 27 Apr 2002 11:28:54 -0500 (CDT) [thread overview]
Message-ID: <m171V4A-0005khC@gherkin.frus.com> (raw)
In-Reply-To: <E171TzX-0008PF-00@the-village.bc.nu> "from Alan Cox at Apr 27, 2002 04:20:03 pm"
Alan Cox wrote:
> > I would like to propose that a clearer, more direct message be used.
> > Something like "Warning: kernel maintainers may not support your kernel
> > since you have loaded %s: %s%s\n" would be much more informative and
> > correct.
>
> More informative but I think too soft. It still implies we might want to
> hear about it but not reply. That isnt the case.
What you say is true enough if you speak for yourself and/or the core
cadre of kernel maintainers. On the other hand, the linux-kernel list
has been and mostly continues to be a good place to get help with
problems related to kernel changes that affect non-GPL modules.
To put it another way, the kernel developers aren't necessarily the
target audience when a request for assistance is posted to linux-kernel.
If that was too subtle, kernel developers aren't the only people who
read linux-kernel. Is linux-kernel an appropriate venue for such
assistance requests? Maybe not the *most* appropriate one, but it's
often the most efficient. Let me put it this way: speaking for myself,
I don't ask linux-kernel list readers for help with a problem if the
problem isn't the immediate result of a kernel change.
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next prev parent reply other threads:[~2002-04-27 16:29 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 4:51 The tainted message Richard Thrapp
2002-04-27 7:50 ` arjan
2002-04-27 8:06 ` Enrico Demarin
2002-04-27 18:45 ` Alan Cox
2002-04-27 12:08 ` Francois Romieu
2002-04-27 15:51 ` Richard Thrapp
2002-04-27 17:02 ` was: " Francois Romieu
2002-04-28 0:33 ` Keith Owens
2002-04-27 15:20 ` Alan Cox
2002-04-27 14:27 ` Martin Dalecki
2002-04-27 18:41 ` Alan Cox
2002-04-27 16:03 ` Richard Thrapp
2002-04-27 16:28 ` Bob_Tracy [this message]
2002-04-27 16:57 ` Robert Love
2002-04-29 16:59 ` Brian Beattie
2002-04-29 17:15 ` tomas szepe
2002-04-29 17:43 ` Ian Molton
2002-04-29 17:41 ` Thomas 'Dent' Mirlacher
2002-04-29 18:16 ` Ian Molton
2002-04-29 18:14 ` tomas szepe
2002-04-29 17:42 ` tomas szepe
2002-04-29 19:11 ` John Alvord
2002-04-29 19:21 ` tomas szepe
2002-04-29 18:41 ` Sandy Harris
2002-04-29 20:00 ` tomas szepe
2002-04-29 23:06 ` Keith Owens
2002-04-29 23:53 ` tomas szepe
2002-04-30 13:37 ` john slee
2002-04-30 13:44 ` Keith Owens
2002-04-29 18:14 ` Christian Bornträger
2002-04-29 17:34 ` Sandy Harris
2002-04-27 19:22 ` Chris Abbey
2002-04-27 19:50 ` Alan Cox
2002-04-28 0:27 ` Keith Owens
2002-04-28 1:27 ` Richard Thrapp
2002-04-28 1:41 ` Keith Owens
2002-04-28 2:14 ` Richard Thrapp
2002-04-28 2:00 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-04-30 8:36 Martin Knoblauch
2002-05-02 7:35 Martin Knoblauch
2002-05-02 11:55 ` Keith Owens
2002-05-02 13:08 ` Martin Knoblauch
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=m171V4A-0005khC@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox