From: ilya@theIlya.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-mips@linux-mips.org
Subject: Re: Broadcom 4702?
Date: Thu, 15 Jan 2004 14:46:27 -0800 [thread overview]
Message-ID: <20040115224627.GC12702@gateway.total-knowledge.com> (raw)
In-Reply-To: <1074202392.2753.2.camel@dhcp23.swansea.linux.org.uk>
I don't really see any problem with that. I think providing it
on web site and listing URL somewhere in manual should be more then
enough.
IANAL, of course.
Ilya.
On Thu, Jan 15, 2004 at 09:33:13PM +0000, Alan Cox wrote:
> This is actually one reason some embedded people have concerns about the
> GPL. It isnt providing the code, its how to handle the offer/provision
> when the product in question is a tea maker or some appliance where it
> isnt natural to ship say an accompanying CD of windows drivers.
>
>
next prev parent reply other threads:[~2004-01-15 22:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 22:00 Broadcom 4702? Charlie Brady
2004-01-13 22:28 ` Jun Sun
2004-01-14 20:49 ` Charlie Brady
2004-01-14 21:05 ` Jim Thompson
2004-01-14 21:15 ` Alan Cox
2004-01-14 21:42 ` Jim Thompson
2004-01-14 22:00 ` Broadcom gcc/binutils mods (Re: Broadcom 4702?) Charlie Brady
2004-01-14 22:53 ` Broadcom 4702? Alan Cox
2004-01-15 1:03 ` Jun Sun
2004-01-15 3:39 ` Charlie Brady
2004-01-15 9:11 ` Dominic Sweetman
2004-01-15 21:33 ` Alan Cox
2004-01-15 22:46 ` ilya [this message]
2004-01-14 21:50 ` Broadcom gcc/binutils changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-14 21:18 ` Broadcom 4702? Jun Sun
2004-01-15 18:53 ` Charlie Brady
2004-01-15 19:14 ` John W. Linville
2004-01-15 20:08 ` Broadcom gcc changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-15 20:18 ` Steven J. Hill
2004-01-15 20:25 ` John W. Linville
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=20040115224627.GC12702@gateway.total-knowledge.com \
--to=ilya@theilya.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@linux-mips.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