From: "H. Peter Anvin" <hpa@zytor.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>, Greg KH <greg@kroah.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] klibc for 2.5.64 - try 2
Date: Fri, 07 Mar 2003 11:42:27 -0800 [thread overview]
Message-ID: <3E68F623.4020701@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303070928560.26430-100000@chaos.physics.uiowa.edu>
Kai Germaschewski wrote:
>
> Correct me, IANAL, but my understanding is that klibc will be dual
> GPL/<whatever it is now> by inclusion into the kernel tree, after all the
> whole purpose is to provide an initramfs which will be linked into vmlinux
> (Yes, linked not in the normal sense, but still).
>
I don't actually think dual licensing is necessary, since the new
BSD/MIT license is generally considered to be GPL-compatible (i.e. it
grants all the rights the GPL does.) The dual license concept dates
back to the "old BSD" license, which definitely was *not* GPL-compatible.
> So it'd rather be similar to some parts of the kernel which are already
> dual licensed (parts of ACPI I think being the latest example), and
> patches will be assumed to be contributed under that dual license, unless
> explicitly stated otherwise.
This is pretty much it, except I believe explicit dual licensing is
superfluous. If anyone has evidence to the contrary please let me know.
-hpa
next prev parent reply other threads:[~2003-03-07 19:33 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 0:16 [BK PATCH] klibc for 2.5.64 - try 2 Greg KH
2003-03-07 1:02 ` Roman Zippel
2003-03-07 1:05 ` H. Peter Anvin
2003-03-07 1:23 ` Roman Zippel
2003-03-07 1:35 ` H. Peter Anvin
2003-03-07 9:55 ` Roman Zippel
2003-03-07 13:43 ` H. Peter Anvin
2003-03-07 15:33 ` Kai Germaschewski
2003-03-07 19:42 ` H. Peter Anvin [this message]
2003-03-07 18:37 ` Roman Zippel
2003-03-07 18:52 ` Linus Torvalds
2003-03-07 21:55 ` Roman Zippel
2003-03-07 23:05 ` Linus Torvalds
2003-03-07 23:36 ` Greg KH
2003-03-07 23:53 ` Linus Torvalds
2003-03-07 23:55 ` Greg KH
2003-03-08 0:47 ` Linus Torvalds
2003-03-08 0:54 ` Greg KH
2003-03-07 23:39 ` Russell King
2003-03-07 23:44 ` H. Peter Anvin
2003-03-08 0:00 ` Russell King
2003-03-08 0:38 ` Roman Zippel
2003-03-08 0:46 ` H. Peter Anvin
2003-03-08 1:27 ` Roman Zippel
2003-03-12 17:27 ` Pavel Machek
2003-03-13 0:22 ` H. Peter Anvin
2003-03-08 0:46 ` David Lang
2003-03-08 1:49 ` Roman Zippel
2003-03-08 2:00 ` David Lang
2003-03-08 2:26 ` Roman Zippel
2003-03-08 16:55 ` Roman Zippel
2003-03-08 17:06 ` Vlad@geekizoid.com
2003-03-08 2:06 ` Eric W. Biederman
[not found] ` <20030308100359.A27153@flint.arm.linux.org.uk>
2003-03-08 15:50 ` Eric W. Biederman
2003-03-08 16:13 ` Russell King
2003-03-08 17:28 ` Eric W. Biederman
2003-03-08 21:08 ` H. Peter Anvin
2003-03-09 2:25 ` Eric W. Biederman
2003-03-09 2:30 ` Larry McVoy
2003-03-09 11:32 ` Daniel Egger
2003-03-09 11:46 ` Eric W. Biederman
2003-03-09 14:19 ` Daniel Egger
2003-03-10 0:49 ` H. Peter Anvin
2003-03-10 1:40 ` Daniel Egger
2003-03-10 6:01 ` Eric W. Biederman
2003-03-10 20:33 ` Hans-Peter Jansen
2003-03-10 22:02 ` Daniel Egger
2003-03-08 20:52 ` H. Peter Anvin
2003-03-08 21:10 ` H. Peter Anvin
2003-03-09 1:29 ` Eric W. Biederman
2003-03-09 1:46 ` H. Peter Anvin
2003-03-09 2:37 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 19:21 Matthew Wilcox
2003-03-07 21:04 ` Alan Cox
[not found] <1047106664.22024.0.camel@rth.ninka.net>
2003-03-08 15:54 ` Linus Torvalds
2003-03-08 16:03 ` David S. Miller
2003-03-08 16:35 ` Linus Torvalds
2003-03-08 16:22 ` David S. Miller
2003-03-08 17:07 ` Larry McVoy
2003-03-08 20:22 ` Linus Torvalds
2003-03-08 21:02 ` H. Peter Anvin
2003-03-08 20:56 ` H. Peter Anvin
2003-03-09 1:24 ` Roman Zippel
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=3E68F623.4020701@zytor.com \
--to=hpa@zytor.com \
--cc=greg@kroah.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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.