From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] nettle: update nettle to version 3.0
Date: Thu, 21 Aug 2014 07:10:38 -0700 [thread overview]
Message-ID: <53F5FDDE.30609@gmail.com> (raw)
In-Reply-To: <1408606690.1669.103.camel@ted>
On 08/21/2014 12:38 AM, Richard Purdie wrote:
> On Sun, 2014-08-17 at 16:06 -0700, Armin Kuster wrote:
>> With this update, LGPLv3 or GPLv3 where added to many files.
>> Each supported algorithms govern which license they want.
>> Many are stated as "ether v2 or v3 or both in parallel".
>> Update license to be v2 or LGPLv3 or GPLv3.
>>
>> The previous verion had one GPLv3 file so the license was incorrect.
>
> With this change, "bitbke gnutls" stops working.
dang.
I will look into it.
- Armin
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2014-08-21 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 23:06 [PATCH v3] nettle: update nettle to version 3.0 Armin Kuster
2014-08-21 7:38 ` Richard Purdie
2014-08-21 14:10 ` akuster808 [this message]
2014-08-21 14:33 ` akuster808
2014-08-21 16:55 ` Otavio Salvador
2014-08-21 19:27 ` akuster808
2014-08-21 20:50 ` Richard Purdie
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=53F5FDDE.30609@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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