From: Richard Thrapp <rthrapp@sbcglobal.net>
To: Keith Owens <kaos@ocs.com.au>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: The tainted message
Date: 27 Apr 2002 20:27:07 -0500 [thread overview]
Message-ID: <1019957228.8818.109.camel@wizard> (raw)
In-Reply-To: <31444.1019953661@ocs3.intra.ocs.com.au>
On Sat, 2002-04-27 at 19:27, Keith Owens wrote:
> On Sat, 27 Apr 2002 16:20:03 +0100 (BST),
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >How about
> >
> >Warning: The module you have loaded (%s) does not seem to have an open
> > source license. Please send any kernel problem reports to the
> > author of this module, or duplicate them from a boot without
> > ever loading this module before reporting them to the community
> > or your Linux vendor
>
> I'm going for the current message followed by "See <URL> for more
> information". <URL> defaults to http://www.tux.org/lkml/#s1-18,
> vendors who want to point to their policy text can override the URL
> when they build modutils.
Why did you tell me to ask here and go with what Alan said if you
weren't going to listen to the discussion? Alan's message corrects all
of the problems we found. Several people agreed on the basic form. If
you weren't going to go with the agreed upon result, why did you have me
ask here? You just wasted a lot of our time. You should have just told
me earlier that you weren't going to correct it -- I would have accepted
the decision.
I get sick and tired of maintainers who solicit opinions and then refuse
to listen to the answers they get back, even when people who know what
they are doing agree... even when the majority agrees. I've seen it
happen many times. I know it's the maintainer's choice in the end, but
don't ask for community opinions unless you're going to listen to them.
It's insulting and infuriating.
As for your correction, people aren't going to look up an URL in
general. It's too inconvenient. Many of them will probably just forget
about the message and report bugs to the wrong place anyway.
I provide a module, not a distribution. I've found that people want to
choose their distribution, even sometimes in embedded space, so I let
them (and I have no interest in providing a distribution anyway). I
cannot control what modutils they run. But I get bug reports back on
the module due to the tainted message.
At the very least, -please- change the verb tense of the message to be
correct. That will at least eliminate the "module doesn't load" bug
reports (I hope).
-- Richard Thrapp
next prev parent reply other threads:[~2002-04-28 1:27 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
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 [this message]
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=1019957228.8818.109.camel@wizard \
--to=rthrapp@sbcglobal.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--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