From: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: When is the kernel moving to GPLv3?
Date: Thu, 16 Nov 2006 09:56:44 -0700 [thread overview]
Message-ID: <455C984C.7080308@wolfmountaingroup.com> (raw)
/"Red Hat has slammed the door shut
<http://www.eweek.com/article2/0,1895,2059675,00.asp> on any possibility
of entering into a patent protection deal similar to the one Microsoft
recently announced with Novell, eWeek is reporting. While Microsoft has
repeatedly said it wants to work with Red Hat and would like to
structure a relationship where its customers can be assured of the same
thing as Novell's customers
<http://linux.slashdot.org/linux/06/11/02/1957252.shtml?tid=109> now
are, Mark Webbink, Red Hat's deputy general counsel, says 'we do not
believe there is a need for or basis for the type of relationship
defined in the Microsoft-Novell announcement.' Interestingly enough,
Microsoft also says that it has not ruled out going it alone and
providing some sort of indemnification for its customers who also use
Red Hat Linux."/
"Meanwhile, Eben Moglen, the FSF general counsel, promises that GPLv3
will explicitly outlaw
<http://money.cnn.com/blogs/legalpad/2006/11/is-microsoft-novell-deal-dead-on.html>
deals like this. (Of course everyone's on v2, so calling the Novell deal
"DOA" would be premature.)"
So when is the kernel moving to GPLv3? I have seen some discussions
about moving off v2, is there concensus about moving to v3 to remove
threats of patent claims against v2 code by M$ and others who may use
Linux in hardware based projects.
Jeff
next reply other threads:[~2006-11-16 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 16:56 Jeffrey V. Merkey [this message]
2006-11-16 15:59 ` When is the kernel moving to GPLv3? (probably feeding a troll :) Lennart Sorensen
2006-11-16 17:13 ` Jeffrey V. Merkey
2006-11-16 16:03 ` [ot] (was When is the kernel moving to GPLv3?) Oleg Verych
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=455C984C.7080308@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.