From: Jun Sun <jsun@mvista.com>
To: Jim Thompson <jimt@vivato.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-mips@linux-mips.org,
Charlie Brady <charlieb-linux-mips@e-smith.com>,
jsun@mvista.com
Subject: Re: Broadcom 4702?
Date: Wed, 14 Jan 2004 17:03:55 -0800 [thread overview]
Message-ID: <20040114170355.G13471@mvista.com> (raw)
In-Reply-To: <7CB2EF32-46DA-11D8-9715-000393C30E1E@vivato.net>; from jimt@vivato.net on Wed, Jan 14, 2004 at 01:42:01PM -0800
On Wed, Jan 14, 2004 at 01:42:01PM -0800, Jim Thompson wrote:
>
> I have binaries. I asked. I was told "no".
>
> On Jan 14, 2004, at 1:15 PM, Alan Cox wrote:
>
> > On Mer, 2004-01-14 at 21:05, Jim Thompson wrote:
> >> My question is why these patches, which are subject to GPL (it is
> >> binutils and gcc, after all), haven't been released.
> >
> > There is no obligation for anyone to provide the source except to those
> > they provide the binaries. They just can't stop those people then
> > redistributing it.
> >
Since we are on this subject, I am curious if I buy a Cisco's router
whether it is considered that Cisco distributs the binaries to me
and whether I can demand for the source code if they are GPL'ed software.
I can see arguments go either way. Do open source community and
industry have some concensus on this issue?
Jun
next prev parent reply other threads:[~2004-01-15 1:04 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 [this message]
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
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=20040114170355.G13471@mvista.com \
--to=jsun@mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=charlieb-linux-mips@e-smith.com \
--cc=jimt@vivato.net \
--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