From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bian Naimeng <biannm@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] libmpc: add a GPLv2 recipe
Date: Thu, 18 Jun 2015 09:15:45 +0100 [thread overview]
Message-ID: <1434615345.14710.49.camel@linuxfoundation.org> (raw)
In-Reply-To: <1434612286-52367-1-git-send-email-biannm@cn.fujitsu.com>
On Thu, 2015-06-18 at 15:24 +0800, Bian Naimeng wrote:
> Same as other recipe such as bash, we should provide both GPLv3 and !GPLv3 recipe
libmpc is not really the same class of recipe as bash. Its mainly used
by gcc and we don't have GPLv2 versions of gcc so this doesn't make much
sense.
Why do you need a GPLv2 version of libmpc?
Cheers,
Richard
prev parent reply other threads:[~2015-06-18 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 7:24 [PATCH 0/2] libmpc: add a GPLv2 recipe Bian Naimeng
2015-06-18 7:24 ` [PATCH 1/2] libmpc: move 'LICENSE' into version specified recipe Bian Naimeng
2015-06-18 7:24 ` [PATCH 2/2] libmpc: add libmpc-0.2 which is a GPLv2 version Bian Naimeng
2015-06-18 8:15 ` Richard Purdie [this message]
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=1434615345.14710.49.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=biannm@cn.fujitsu.com \
--cc=openembedded-core@lists.openembedded.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