From: Mark Mielke <mark@mark.mielke.cc>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: "Rose, Billy" <wrose@loislaw.com>,
"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
Roman Zippel <zippel@linux-m68k.org>,
"'Karim Yaghmour'" <karim@opersys.com>,
yodaiken@fsmlabs.com, linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: Wed, 29 May 2002 15:58:10 -0400 [thread overview]
Message-ID: <20020529155810.B22536@mark.mielke.cc> (raw)
In-Reply-To: <4188788C3E1BD411AA60009027E92DFD0962E2F2@loisexc2.loislaw.com> <E17D9PC-0006in-00@starship>
On Wed, May 29, 2002 at 09:46:46PM +0200, Daniel Phillips wrote:
> What we're really discussing is whether we're willing to allow patent
> restrictions to inhibit the growth of Linux in new areas that go beyond
> its traditional IT role, and further, whether we're willing to accept
> such restrictions from people or companies that depend on Linux for
> their sustenance, and who have benefitted from the lack of such
> restrictions as they wish to impose on others.
Unless Linux is released under a stricter license, I don't know how much
effect 'whether we're willing to accept such restrictions' will have.
People can theorize that software patents make no sense, but that opinion
alone does not invalidate them.
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-05-29 20:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 12:36 Rose, Billy
2002-05-29 19:46 ` Daniel Phillips
2002-05-29 19:58 ` Mark Mielke [this message]
-- strict thread matches above, loose matches on Subject: below --
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
[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
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
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=20020529155810.B22536@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=wrose@loislaw.com \
--cc=yodaiken@fsmlabs.com \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®