All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/13] Jethro-next pull request
Date: Fri, 23 Sep 2016 23:24:34 +0100	[thread overview]
Message-ID: <1474669474.30475.8.camel@linuxfoundation.org> (raw)
In-Reply-To: <82a667ae-827f-3def-d59a-3ac86b406d62@gmail.com>

On Fri, 2016-09-23 at 10:23 -0700, akuster808 wrote:
> On 09/18/2016 03:44 PM, Armin Kuster wrote:
> > 
> > From: Armin Kuster <akuster@mvista.com>
> > 
> > please consider these security and bug fixes for Jethro.
> > 
> > My krogoth-next stagging branch has a complimentary set for the
> > security fixes.
> > 
> > http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akust
> > er/krogoth-next: 7a24bd8a38a2819965b8c1926d33042bd61d1f0b
> > 
> > The following changes since commit
> > 6b732a392289a7bb50b0e3716c066c62fa32a14d:
> > 
> >    curl: security fix for CVE-2016-5420 (2016-09-02 08:48:20 +0100)
> > 
> > are available in the git repository at:
> > 
> >    git://git.openembedded.org/openembedded-core-contrib
> > akuster/jethro-next
> >    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/
> > log/?h=akuster/jethro-next

I've merged in the various jethro bitbake/core fixes, thanks. Sorry
about the delay, I think we're up to date now?

Cheers,

Richard


      reply	other threads:[~2016-09-23 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18 22:44 [PATCH 00/13] Jethro-next pull request Armin Kuster
2016-09-23 17:23 ` akuster808
2016-09-23 22:24   ` 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=1474669474.30475.8.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster808@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.