From: Adrian McMenamin <adrian@mcmen.demon.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: a3load.hex
Date: Mon, 17 Oct 2005 18:59:42 +0000 [thread overview]
Message-ID: <1129575583.3367.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20051014134617.42227.qmail@web30703.mail.mud.yahoo.com>
On Mon, 2005-10-17 at 11:45 -0700, Greg KH wrote:
>
> They did rewrite it. Have you looked at the version in our cvs tree:
> http://cvs.sourceforge.net/viewcvs.py/linux-hotplug/fxload/a3load.hex?rev=1.1&view=auto
>
> What is wrong with that?
Actually, their licence is rubbish in that it claims to over rule
statute law. I cannot believe their is a jurisdiction on the planet that
allows some lawyer working for a hardware company set the decisions of
their legislature at null and void!
The writers of the GPL specifically avoided this as they knew it could
be used to destroy the validity of the licence as a whole.
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-10-17 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 13:46 a3load.hex william baroniunas
2005-10-14 21:13 ` a3load.hex Greg KH
2005-10-15 17:27 ` a3load.hex Adrian McMenamin
2005-10-17 13:14 ` a3load.hex william baroniunas
2005-10-17 18:45 ` a3load.hex Greg KH
2005-10-17 18:59 ` Adrian McMenamin [this message]
2005-10-17 19:57 ` a3load.hex Darren Salt
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=1129575583.3367.13.camel@localhost.localdomain \
--to=adrian@mcmen.demon.co.uk \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).