From: "David S. Miller" <davem@redhat.com>
To: zippel@linux-m68k.org
Cc: lm@bitmover.com, pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: Bitkeeper licence issues
Date: Mon, 18 Mar 2002 17:37:20 -0800 (PST) [thread overview]
Message-ID: <20020318.173720.123672354.davem@redhat.com> (raw)
In-Reply-To: <3C9691C8.51A4A504@linux-m68k.org>
From: Roman Zippel <zippel@linux-m68k.org>
Date: Tue, 19 Mar 2002 02:18:00 +0100
That's someone, who doesn't understand what free software is about and
desperately looking for someone to blame it on.
What are you trying to tell us?
Roman, how do you pay for things like FOOD and a place to LIVE?
Who does what kind of work to provide the money you need for
the basic necessities in life?
Unfortunately, the real economics of the world right now does not make
it so that every programmer can work on %100 free software for a
living like I do.
That is a fact.
Given that, most programmers have to find another way to put food into
their stoamches and have a horizontal surface to sleep on at night.
The person who wrote the article in question may have a few
inaccuracies about how free software works, I'll give you that,
but that guy has a perfect understand about how REAL LIFE works.
That is where you need understand things better.
next prev parent reply other threads:[~2002-03-19 1:41 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 21:26 Bitkeeper licence issues Pavel Machek
2002-03-18 22:42 ` Larry McVoy
2002-03-18 23:14 ` Pavel Machek
2002-03-18 23:22 ` Dave Jones
2002-03-18 23:43 ` Pavel Machek
2002-03-19 8:35 ` Rik van Riel
2002-03-19 2:02 ` Larry McVoy
2002-03-19 8:21 ` Gerd Knorr
2002-03-19 15:11 ` Larry McVoy
2002-03-19 21:58 ` Pavel Machek
2002-03-19 22:04 ` Larry McVoy
[not found] ` <20020319215800.GN12260@atrey.karlin.m__.cuni.cz>
2002-03-20 22:42 ` Ton Hospel
2002-03-19 22:06 ` Pavel Machek
2002-03-19 23:25 ` Larry McVoy
2002-03-19 23:27 ` David S. Miller
2002-03-19 23:44 ` Larry McVoy
2002-03-19 23:45 ` David S. Miller
2002-03-19 23:54 ` Matthew Kirkwood
2002-03-19 23:56 ` Ben Collins
2002-03-20 17:23 ` Martin Dalecki
2002-03-20 17:51 ` Alan Cox
2002-03-20 18:04 ` Martin Dalecki
2002-03-20 20:34 ` Neil Booth
2002-03-19 23:34 ` Tom Rini
2002-03-20 0:09 ` Alan Cox
2002-03-24 11:44 ` Thunder from the hill
2002-03-20 7:57 ` Alexander Viro
2002-03-19 0:00 ` yodaiken
2002-03-19 1:29 ` David S. Miller
2002-03-19 1:18 ` Roman Zippel
2002-03-19 1:37 ` David S. Miller [this message]
2002-03-19 18:42 ` Roman Zippel
2002-03-19 19:09 ` Alan Cox
2002-03-19 20:01 ` Shane Nay
2002-03-19 23:08 ` Rik van Riel
2002-03-19 23:19 ` Robert Love
2002-03-19 23:26 ` Rik van Riel
2002-03-19 23:42 ` Davide Libenzi
2002-03-19 23:31 ` yodaiken
2002-03-19 23:47 ` Larry McVoy
2002-03-20 0:02 ` Thomas Dodd
2002-03-20 0:19 ` Theodore Tso
2002-03-20 0:57 ` Petko Manolov
2002-03-21 19:44 ` Mark H. Wood
2002-03-21 20:29 ` Shane Nay
2002-03-27 14:40 ` Henning P. Schmiedehausen
2002-03-20 0:05 ` James Simmons
2002-03-19 20:35 ` Andreas Dilger
2002-03-20 0:14 ` Kurt Ferreira
2002-03-20 2:16 ` Greg Hennessy
2002-03-20 0:57 ` Richard Gooch
2002-03-21 19:14 ` Roman Zippel
2002-03-21 20:54 ` Alan Cox
2002-03-22 0:02 ` Roman Zippel
2002-03-19 1:44 ` Anton Altaparmakov
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=20020318.173720.123672354.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=pavel@ucw.cz \
--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