Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] opensp and openssh recipe upgrades
Date: Tue, 08 May 2012 16:20:14 +0100	[thread overview]
Message-ID: <1336490414.30349.5.camel@ted> (raw)
In-Reply-To: <cover.1336430865.git.scott.a.garman@intel.com>

On Mon, 2012-05-07 at 15:49 -0700, Scott Garman wrote:
> Hello,
> 
> This pull request includes upgrades for the opensp and openssh recipes.
> They have been build-tested on all 5 of our QEMU architectures. The
> distro tracking updates include a couple of recipes that I missed in
> previous pull requests.
> 
> Scott
> 
> The following changes since commit 2929e7d590862d9649458c90804e79a1dce40423:
> 
>   glib-2.0: Fix issues with libelf dependency creeping in (2012-05-07 10:53:24 +0100)
> 
> are available in the git repository at:
>   git://git.pokylinux.org/poky-contrib sgarman/recipe-upgrades-oe
>   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/recipe-upgrades-oe
> 
> Scott Garman (3):
>   openssh: upgrade to 6.0p1
>   opensp: upgrade to 1.5.2
>   distro_tracking: updates for upgraded recipes

Merged to master, thanks.

Richard




      parent reply	other threads:[~2012-05-08 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 22:49 [PATCH 0/3] opensp and openssh recipe upgrades Scott Garman
2012-05-07 22:49 ` [PATCH 1/3] openssh: upgrade to 6.0p1 Scott Garman
2012-05-07 22:49 ` [PATCH 2/3] opensp: upgrade to 1.5.2 Scott Garman
2012-05-07 22:49 ` [PATCH 3/3] distro_tracking: updates for upgraded recipes Scott Garman
2012-05-08 15:20 ` 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=1336490414.30349.5.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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