From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "www.sveasoft.com" <james.ewing@sveasoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: WRT54G
Date: Wed, 22 Sep 2004 15:08:10 +0100 [thread overview]
Message-ID: <1095862089.4516.30.camel@localhost.localdomain> (raw)
In-Reply-To: <03c501c4a077$9530c410$0901a8c0@test>
On Mer, 2004-09-22 at 08:41, www.sveasoft.com wrote:
> Why folks insist on mirroring unstable, development code that include
> additions we have specifically not licensed for redistribution until stable
> under the guise that the GPL gives them this right is beyond my
> comprehension. Perhaps gurus like Alan C. can explain why our model is evil
> and we should be done away with and why the GPL gives these folks this
> right?
Thanks for clarifying all this. I'm not going to tell anyone their
business model is evil (well unless it includes things like shooting
Colombian trade unionists to keep drink prices down).
What you do with code you created, and which isn't derivative of other
code is -your business-. A lot of free software people do ask that it is
made clear which bits are free and which are not. I've never looked at
your development code to know how you handle this.
Alan
next prev parent reply other threads:[~2004-09-22 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 7:41 WRT54G www.sveasoft.com
2004-09-22 9:55 ` WRT54G Daniel Egger
2004-09-22 14:08 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-19 9:58 WRT54G Aiko Barz
2004-09-20 13:13 ` WRT54G Alan Cox
2004-09-21 12:10 ` WRT54G Daniel Egger
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=1095862089.4516.30.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=james.ewing@sveasoft.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