From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] long long warning
Date: Wed, 20 Mar 2002 07:40:36 +0000 [thread overview]
Message-ID: <20020320074036.9184119A65@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
I think it's that a GNU Free™ lunch is not free in the financial
sense, but if you sell someone lunch, you must also give them the
means to recreate the lunch, and to sell it to other people. I've
coined the term GNU Recipe™ to cover this.
You can, of course, sell the lunch for outrageous sums. The lunch
need not be any good either. But it is Free™.
Yours in horrible anticipation of serious replies to this,
Nigel
[-- Attachment #2: Type: message/rfc822, Size: 1418 bytes --]
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] long long warning
Date: Tue, 19 Mar 2002 22:55:53 -0800
Message-ID: <20020320065639.7813419A7B@mail.cse.psu.edu>
> There may well be if you take the FSF definition of free.
So a GNU Free™ lunch is one that you are obligated to pass on to
others after eating it? Or perhaps before eating it?
next reply other threads:[~2002-03-20 7:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 7:40 nigel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-22 6:14 David Gordon Hogan
2002-03-21 3:31 dmr
2002-03-21 4:06 ` George Michaelson
2002-03-21 11:02 ` Thomas Bushnell, BSG
2002-03-20 18:18 markp
2002-03-21 7:50 ` skipt
2002-03-20 14:49 Russ Cox
2002-03-20 10:55 forsyth
2002-03-20 6:55 Geoff Collyer
2002-03-20 9:43 ` Thomas Bushnell, BSG
2002-03-19 14:03 nigel
2002-03-19 13:56 Peter Bosch
2002-03-20 9:43 ` Thomas Bushnell, BSG
2002-03-19 10:45 forsyth
2002-03-19 17:28 ` Dan Cross
2002-03-15 16:26 presotto
2002-03-15 14:07 presotto
2002-03-15 16:20 ` Scott Schwartz
2002-03-18 10:34 ` ozan s. yigit
2002-03-18 17:37 ` Thomas Bushnell, BSG
2002-03-18 18:08 ` skipt
2002-03-19 9:49 ` Thomas Bushnell, BSG
2002-03-19 17:11 ` Dan Cross
2002-03-19 9:49 ` ozan s yigit
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=20020320074036.9184119A65@mail.cse.psu.edu \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.edu \
/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).