From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: libfdt: going forward for u-boot
Date: Thu, 22 Mar 2007 12:16:09 +0100 [thread overview]
Message-ID: <ed13d3cfd27edb956a4f3d4bb59a135a@kernel.crashing.org> (raw)
In-Reply-To: <20070322004959.GE2295@localhost.localdomain>
>> One thought that occurred to me since we last discussed this is to
>> relicense it LGPL. That way it could be linked into proprietary code
>> without having to maintain a dual license and the copyright assignment
>> headaches that come with outside contributors.
>
> Heh. The lawyers suggested that too, but I talked them out of it.
> The trouble with LGPL is that to satisfy its conditions you need to be
> pretty careful about how you link things together.
Yeah, the LGPL is even more work for lawyers than the GPL.
You could try a BSD- or MIT-style license perhaps, those
are *really* easy to understand, even to lawyers :-)
Segher
next prev parent reply other threads:[~2007-03-22 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 0:08 libfdt: going forward for u-boot Jerry Van Baren
2007-03-22 0:49 ` David Gibson
2007-03-22 1:12 ` Jerry Van Baren
2007-03-22 1:25 ` David Gibson
2007-03-22 1:37 ` Jerry Van Baren
2007-03-22 1:49 ` David Gibson
2007-03-22 11:16 ` Segher Boessenkool [this message]
2007-03-22 16:42 ` Hollis Blanchard
2007-03-23 4:17 ` David Gibson
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=ed13d3cfd27edb956a4f3d4bb59a135a@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.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).