public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: The tainted message
Date: Thu, 02 May 2002 15:08:05 +0200	[thread overview]
Message-ID: <3CD13A35.1036639@TeraPort.de> (raw)
In-Reply-To: <28821.1020340504@ocs3.intra.ocs.com.au>

Keith Owens wrote:
> 
> On Thu, 02 May 2002 09:35:36 +0200,
> Martin Knoblauch <Martin.Knoblauch@TeraPort.de> wrote:
> > purely technical question: does this work with the "compatible" license
> >strings without making them incompatible? E.g. would this be a
> >compatible license:
> >
> >MODULE_LICENSE("GPL - contact someone@somewhere for support");
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=99926682329331&w=2

 OK, if I read this correctly, the suggestion of a MODULE_SUPPORT tag
makes a lot of sense. Although, one could (mis)use the MODULE_AUTHOR for
it.

 Given the sloppyness/lazyness of people/programmes in general, use of
MODULE_LICENSE, MODULE_AUTHOR and MODULE_DESCRIPTION should be enforced
at compile time.

Martin
-- 
------------------------------------------------------------------
Martin Knoblauch         |    email:  Martin.Knoblauch@TeraPort.de
TeraPort GmbH            |    Phone:  +49-89-510857-309
C+ITS                    |    Fax:    +49-89-510857-111
http://www.teraport.de   |    Mobile: +49-170-4904759

  reply	other threads:[~2002-05-02 13:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02  7:35 The tainted message Martin Knoblauch
2002-05-02 11:55 ` Keith Owens
2002-05-02 13:08   ` Martin Knoblauch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-30  8:36 Martin Knoblauch
2002-04-27  4:51 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-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
2002-04-28  2:00       ` Alan Cox

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=3CD13A35.1036639@TeraPort.de \
    --to=martin.knoblauch@teraport.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.knoblauch@TeraPort.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