public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 21:14:19 -0500	[thread overview]
Message-ID: <1019960059.8818.149.camel@wizard> (raw)
In-Reply-To: <32711.1019958090@ocs3.intra.ocs.com.au>

Keith, I apologize for my rash words.  I clicked send before I cooled
down, and I should know better.  I care a lot about my work.  I am
sorry.

On Sat, 2002-04-27 at 20:41, Keith Owens wrote:
> On 27 Apr 2002 20:27:07 -0500, 
> Richard Thrapp <rthrapp@sbcglobal.net> wrote:
> >On Sat, 2002-04-27 at 19:27, Keith Owens wrote:
> That is one of the many costs you have to bear for shipping binary only
> modules.  I am not going to make life easier for you.  In your original
> message to me you made no mention of the fact that you are shipping
> binary only modules, if I had know that in advance I would not have
> tried to help you, now you have no credibility with me.

I thought it was pretty obvious that I was shipping a non-GPL module
(not binary-only).  But that is not my only interest.  I have given time
and thought to many open source projects.  I genuinely wanted a more
informative error 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).
> 
> The verb tense is correct.  The message is issued before the module is
> loaded and descibes what is about to occur.

>From the point of view of the user, who sees the message after the
module is loaded, it is incorrect and implies that the module wasn't
loaded.

-- Richard Thrapp



  reply	other threads:[~2002-04-28  2:14 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
2002-04-28  1:41       ` Keith Owens
2002-04-28  2:14         ` Richard Thrapp [this message]
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=1019960059.8818.149.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