From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <claudio.fontana@huawei.com>,
hw.claudio@gmail.com, Luiz Capitulino <lcapitulino@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Gonglei <arei.gonglei@huawei.com>,
qemu-devel@nongnu.org, karl@freefriends.org
Subject: Re: [Qemu-devel] [RFC v5 1/2] util: add memmem replacement function
Date: Fri, 15 May 2015 16:12:14 +0200 [thread overview]
Message-ID: <5555FEBE.5040007@redhat.com> (raw)
In-Reply-To: <5555FB55.5070909@huawei.com>
On 15/05/2015 15:57, Claudio Fontana wrote:
> The header here mentions GPLv2+, but the module data for memmem in gnulib mentions LGPLv2+.
>
> Very confusing.
>
> The COPYING file in gnulib mentions:
>
> "The files in here are mostly copyright (C) Free Software Foundation, and
> are under assorted licenses. Mostly, but not entirely, GPL.
>
> Many modules are provided dual-license, either GPL or LGPL at your
> option. The headers of files in the lib directory (e.g., lib/error.c)
> state GPL for convenience, since the bulk of current gnulib users are
> GPL'd programs. But the files in the modules directory (e.g.,
> modules/error) state the true license of each file, [...]
> "
>
> So if one would want to include the gnulib code without using the gnulib esoteric modules mechanisms, what should one do?
Change it manually, I guess.
Paolo
> CCing Karl Berry since he probably knows what's going on here..
next prev parent reply other threads:[~2015-05-15 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 12:25 [Qemu-devel] [RFC v5 0/2] monitor: add memory search commands s, sp hw.claudio
2015-05-15 12:25 ` [Qemu-devel] [RFC v5 1/2] util: add memmem replacement function hw.claudio
2015-05-15 13:57 ` Claudio Fontana
2015-05-15 14:12 ` Paolo Bonzini [this message]
2015-05-15 14:56 ` Eric Blake
2015-05-15 15:13 ` Claudio Fontana
2015-05-15 16:01 ` Eric Blake
2015-05-18 8:36 ` Claudio Fontana
2015-05-15 12:25 ` [Qemu-devel] [RFC v5 2/2] monitor: add memory search commands s, sp hw.claudio
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=5555FEBE.5040007@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=claudio.fontana@huawei.com \
--cc=hw.claudio@gmail.com \
--cc=karl@freefriends.org \
--cc=lcapitulino@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).