From: Lee Revell <rlrevell@joe-job.com>
To: mmoneta@optonline.net
Cc: linux-kernel@vger.kernel.org, andersen@codepoet.org
Subject: Re: ZyXEL Kernel /BusyBox GPL violation?
Date: Mon, 25 Jul 2005 23:28:03 -0400 [thread overview]
Message-ID: <1122348483.1472.90.camel@mindpipe> (raw)
In-Reply-To: <1122348062.26341.50.camel@mmouse.moneta.optonline.net>
On Mon, 2005-07-25 at 23:21 -0400, Mace Moneta wrote:
> The response seems meaningless; does this constitute a violation of
> GPL?
> If so what, if any, action needs to be taken?
It sounds like they think you are asking for their userspace source
code, or that support rep does not know the difference.
Also if they didn't modify the kernel, they don't have to give you
source, they can just refer you to kernel.org.
Lee
next prev parent reply other threads:[~2005-07-26 3:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 3:21 ZyXEL Kernel /BusyBox GPL violation? Mace Moneta
2005-07-26 3:28 ` Lee Revell [this message]
2005-07-26 5:42 ` Stephen Pollei
2005-07-26 16:15 ` David Schwartz
2005-07-26 17:07 ` linux-os (Dick Johnson)
2005-07-26 17:43 ` Mace Moneta
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=1122348483.1472.90.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmoneta@optonline.net \
/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