From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] nettle: update nettle to version 3.0
Date: Thu, 21 Aug 2014 21:50:32 +0100 [thread overview]
Message-ID: <1408654232.1669.123.camel@ted> (raw)
In-Reply-To: <53F64823.7070705@gmail.com>
On Thu, 2014-08-21 at 12:27 -0700, akuster808 wrote:
>
> On 08/21/2014 09:55 AM, Otavio Salvador wrote:
> > On Thu, Aug 21, 2014 at 11:33 AM, akuster808 <akuster808@gmail.com> wrote:
> >>
> >>
> >> 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.
> >>>
> >>
> >> gnutls is targeting to port to nettle 3.0 in gnutls version 3.4.
> >>
> >> what should I do?
> >
> > Revert for now? :)
>
> Its only in the patch queue from what i can tell. Do I ask for it to be
> dropped or do send a 'revert' patch for the patch?
It didn't make it into master, so no, nothing to be done.
Cheers,
Richard
prev parent reply other threads:[~2014-08-21 20:50 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
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 [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=1408654232.1669.123.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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