From: Dominique Michel <dominique.michel@citycable.ch>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Watch out for license changes to GPL-3.
Date: Tue, 10 Jul 2007 19:10:35 +0200 [thread overview]
Message-ID: <20070710191035.2dfcfa98@localhost> (raw)
In-Reply-To: <20070709212456.GA22067@kroah.com>
> > Can you explain more. If the kernel can be tivoized by someone
>
> I'm sorry, but "tivoized" is not a verb. Please explain what you mean
> by this.
I mean if someone distribute a kernel with a licence that forbid to remove the
functions he added even if we don't want them (as example drm at the kernel
level as in Vista),
>
> > , who will use this kernel? How can this affect the software xyz that
> > have a v3 licence?
>
> I do not understand the question, can you reprase it?
>
who will use this kernel when we can get a vanilla kernel and plenty of
patches and do whatever we want to do with them?
Will this affect the licencing or the distribution of the software xyz?
> thanks,
>
> greg k-h
You are welcome,
Dominique
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-10 17:18 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 18:21 [gentoo-dev] app-arch/cpio-2.9 is now GPLv3 David
2007-07-07 18:35 ` [gentoo-dev] Watch out for license changes to GPL-3 Petteri Räty
2007-07-07 21:26 ` David
2007-07-08 10:28 ` [gentoo-dev] " Steve Long
2007-07-08 11:04 ` [gentoo-dev] " Marijn Schouten (hkBst)
2007-07-08 11:50 ` Wulf C. Krueger
2007-07-08 13:06 ` Seemant Kulleen
2007-07-08 14:46 ` Dominique Michel
2007-07-08 14:51 ` Ciaran McCreesh
2007-07-08 18:15 ` Harald van Dijk
2007-07-08 18:52 ` Wulf C. Krueger
2007-07-08 19:12 ` Harald van Dijk
2007-07-08 19:43 ` Wulf C. Krueger
2007-07-08 20:17 ` Harald van Dijk
2007-07-08 17:48 ` Seemant Kulleen
2007-07-08 18:15 ` Richard Freeman
2007-07-09 0:04 ` [gentoo-dev] " Duncan
2007-07-09 9:31 ` Steve Long
2007-07-09 15:13 ` Duncan
2007-07-09 16:27 ` Jeroen Roovers
2007-07-09 16:43 ` Petteri Räty
2007-07-09 19:37 ` Dominique Michel
2007-07-10 9:30 ` Duncan
[not found] ` <20070709163914.GB16617@kroah.com>
2007-07-09 19:07 ` [gentoo-dev] " Dominique Michel
2007-07-09 21:24 ` Greg KH
2007-07-10 17:10 ` Dominique Michel [this message]
2007-07-10 18:11 ` Greg KH
2007-07-10 20:37 ` Kevin Lacquement
2007-07-10 20:49 ` Greg KH
2007-07-12 9:18 ` [gentoo-dev] " Steve Long
2007-07-12 18:24 ` Chris Gianelloni
2007-07-12 18:31 ` Ciaran McCreesh
2007-07-12 19:00 ` Mike Frysinger
2007-07-12 19:07 ` Ciaran McCreesh
2007-07-12 19:14 ` Seemant Kulleen
2007-07-12 19:27 ` Ciaran McCreesh
2007-07-12 19:48 ` Wulf C. Krueger
2007-07-12 20:02 ` Ciaran McCreesh
2007-07-12 19:58 ` Chris Gianelloni
2007-07-12 20:12 ` Ciaran McCreesh
2007-07-12 20:17 ` Petteri Räty
2007-07-12 20:46 ` Harald van Dijk
2007-07-13 2:56 ` Jeroen Roovers
2007-07-12 20:10 ` Mike Frysinger
2007-07-12 20:16 ` Ciaran McCreesh
2007-07-12 21:06 ` Mike Frysinger
2007-07-12 21:11 ` Ciaran McCreesh
2007-07-12 21:32 ` Mike Frysinger
2007-07-13 2:53 ` Jeroen Roovers
2007-07-13 3:26 ` Mike Frysinger
2007-07-13 3:55 ` Marius Mauch
2007-07-13 4:20 ` Jeroen Roovers
2007-07-13 5:16 ` Mike Frysinger
2007-07-14 2:26 ` [gentoo-dev] " Steve Long
2007-07-12 22:33 ` Steve Long
2007-07-12 18:43 ` [gentoo-dev] " Greg KH
2007-07-12 22:56 ` [gentoo-dev] " Steve Long
2007-07-12 23:49 ` Greg KH
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=20070710191035.2dfcfa98@localhost \
--to=dominique.michel@citycable.ch \
--cc=gentoo-dev@lists.gentoo.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