The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [TUHS] Lexical comparator, was Re: the battle against SCO
Date: Mon, 15 Sep 2003 22:11:41 -0400	[thread overview]
Message-ID: <20030916021555.EFF121EB2@minnie.tuhs.org> (raw)

Robert Brockway:

  Hi.  Don't want to nitpick here but many of us think it is important to
  get this point straight whenever we are talking about GPLed code.  The
  kernel is licenced (as I'm sure you know).  What we are of course
  concerned about is:

  a) Code which is licenced in a manner incompatible with the GPL

  b) Code that the copyright holder did not authorise going into the kernel.

  I'm sure you were just speaking in shorthand but it is subtle point that
  many misinterpret.  Many people outside the OSS community think that "all
  that free code" is in the public domain, which it is most definately not.

====

Quite right.  I wasn't speaking in shorthand, I was speaking in
clumsy; what I should have written is `possible that code restricted
by the System V license got into the system.'

Licenses come in all flavours, and whether there is any license
at all is not the issue here.  I certainly didn't mean, for
example, to imply that all licenses are evil, reptilian kitten-
eaters from another planet.

Norman Wilson
Toronto ON


             reply	other threads:[~2003-09-16  2:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16  2:11 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-16  0:02 Norman Wilson
2003-09-16  1:35 ` Robert Brockway
2003-09-16  3:10   ` M. Warner Losh
2003-09-15 20:39 [TUHS] Fwd: Helping in " Norman Wilson
2003-09-15 22:48 ` [TUHS] Lexical comparator, was " Warren Toomey
2003-09-16  0:46   ` Rhys Weatherley

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=20030916021555.EFF121EB2@minnie.tuhs.org \
    --to=norman@nose.cs.utoronto.ca \
    /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;
as well as URLs for NNTP newsgroup(s).