linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dana Lacoste <dana.lacoste@peregrine.com>
Cc: Mark Mielke <mark@mark.mielke.cc>, linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: 29 May 2002 16:31:44 +0100	[thread overview]
Message-ID: <1022686304.9255.236.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <1022682030.9044.8.camel@dlacoste.ottawa.loran.com>

On Wed, 2002-05-29 at 15:20, Dana Lacoste wrote:
> I wish it weren't so, but it IS.  If RedHat is filing patents, then
> it's fairly apparent that RedHat thinks so too, isn't it?

Strange line of reasoning. Red Hat is an open source company. It doesn't
have a proprietary installer, random bits of the binaries and libraries
that are licensed per seat, embedded setups that happen to generate
partially non free per unit licensed embedded targets.

There are years old Cygnus patents on bits of gcc, there are current Red
Hat filed patents with GPL grants, there are countless thousands of IBM
patents a few of which have GPL grants. People keep assuming this is
something new, yet I would not be suprised if some of the gcc related
patents pre-date Red Hat's existance.


  parent reply	other threads:[~2002-05-29 14:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57.c083d0f.2a237c49@aol.com>
2002-05-27 12:36 ` RTAI/RtLinux Wolfgang Denk
2002-05-28 12:04   ` A reply on the RTLinux discussion yodaiken
2002-05-28 14:37     ` Roman Zippel
2002-05-28 15:57       ` Alan Cox
2002-05-28 15:11         ` Roman Zippel
2002-05-28 16:45           ` Alan Cox
2002-05-29  0:31             ` Roman Zippel
2002-05-29  1:34               ` Mark Mielke
2002-05-29  3:11                 ` Karim Yaghmour
2002-05-29  8:53                   ` Zwane Mwaikambo
2002-05-29 13:54                 ` Dana Lacoste
2002-05-29 15:17                   ` Alan Cox
2002-05-29 14:20                     ` Dana Lacoste
2002-05-29 15:15                       ` Mark Mielke
2002-05-29 17:43                         ` Dana Lacoste
2002-05-29 18:26                           ` Mark Mielke
2002-05-29 15:31                       ` Alan Cox [this message]
2002-05-29 15:45                       ` yodaiken
2002-05-29 17:40                         ` Dana Lacoste
2002-06-03 10:09                       ` Rob Landley
2002-05-29 13:24               ` Alan Cox
2002-05-29 13:43                 ` Roman Zippel
2002-05-29 14:59                   ` Alan Cox
2002-05-29 20:18                     ` Roman Zippel
2002-05-31 11:57                 ` Pavel Machek
2002-05-31 21:34                   ` Mark Mielke
2002-05-31 23:19                   ` yodaiken
2002-05-28 15:19     ` Karim Yaghmour
2002-05-28 15:39       ` Mark Mielke
2002-05-28 16:00         ` Karim Yaghmour
2002-06-01 20:37       ` Michael Barabanov
2002-05-28 16:12 James Bottomley
2002-05-28 17:31 ` Roman Zippel
2002-05-28 18:03   ` James Bottomley
2002-05-28 21:21     ` Jeff V. Merkey
2002-05-29  8:58       ` Peter Wächtler
2002-05-29 12:36 Rose, Billy
2002-05-29 19:46 ` Daniel Phillips
2002-05-29 19:58   ` Mark Mielke

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=1022686304.9255.236.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dana.lacoste@peregrine.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@mark.mielke.cc \
    /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).