From: Mark Mielke <mark@mark.mielke.cc>
To: Dana Lacoste <dana.lacoste@peregrine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: Wed, 29 May 2002 14:26:08 -0400 [thread overview]
Message-ID: <20020529142449.A22536@mark.mielke.cc> (raw)
In-Reply-To: <Pine.LNX.4.21.0205281702540.17583-100000@serv> <1022604318.4123.114.camel@irongate.swansea.linux.org.uk> <3CF42179.29A2CAED@linux-m68k.org> <20020528213457.A22540@mark.mielke.cc> <1022680446.9043.5.camel@dlacoste.ottawa.loran.com> <1022685475.4124.229.camel@irongate.swansea.linux.org.uk> <1022682030.9044.8.camel@dlacoste.ottawa.loran.com> <20020529111553.A15457@mark.mielke.cc> <1022694198.8950.46.camel@dlacoste.ottawa.loran.com>
On Wed, May 29, 2002 at 01:43:18PM -0400, Dana Lacoste wrote:
> Do you see what I'm getting at now? When a party chooses Linux
> for their platform they're choosing all of it, and maybe they'll
> be taking Victor's stuff along with the rest simply because it's
> the rest that they _really_ want.
> Why should Victor be making money off your work?
1) I was not aware that 'Linux' came with Victor's stuff.
2) If I was truly an Open Source priest, I would not care whether
another person made money off my work. Only non-Open Source
priests, or fake Open Source priests are concerned with such
things. Any true Open Source priest knows that people will not
use non-Open Source products by the end of this millenia.
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 18:31 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 [this message]
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
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=20020529142449.A22536@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=dana.lacoste@peregrine.com \
--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
all inboxes | Powered by JetHome®