All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4]Recipe upgrades
Date: Tue, 04 Oct 2011 21:10:07 -0700	[thread overview]
Message-ID: <4E8BD89F.70306@intel.com> (raw)
In-Reply-To: <cover.1317370299.git.lei.mei@intel.com>

On 09/30/2011 01:16 AM, Mei Lei wrote:
> This commit includes some recipes upgrade: curl,diffutils,dropbear.
> And update the distro_tracking_fields.inc
>
> Thanks,
> Lei
>
> The following changes since commit 96241de59fdf548ae0f80cc9e4668f9ba11924ef:
>    Matthew McClintock (1):
>          Fix flac build on e500mc cores
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib lmei3/upgrade-0928
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=lmei3/upgrade-0928
>
> Mei Lei (4):
>    curl: Upgrade from 7.21.7 to 7.22.0
>    diffutils: Upgrade from 3.0 to 3.2.
>    dropbear: Upgrade from 0.52 to 0.53.1
>    distro_tracking_fields.inc: Update upgrade information
>
>   .../conf/distro/include/distro_tracking_fields.inc |   25 +++++++++--------
>   .../configure.patch                                |    0
>   meta/recipes-core/dropbear/dropbear.inc            |    1 +
>   .../dropbear/dropbear/allow-nopw.patch             |   14 +++++-----
>   .../dropbear-0.53.1-static_build_fix.patch         |   29 ++++++++++++++++++++
>   .../urandom-xauth-changes-to-options.h.patch       |   11 ++++---
>   meta/recipes-core/dropbear/dropbear_0.52.bb        |    6 ----
>   meta/recipes-core/dropbear/dropbear_0.53.1.bb      |    6 ++++
>   .../{diffutils_3.0.bb =>  diffutils_3.2.bb}         |    4 +-
>   .../curl/{curl_7.21.7.bb =>  curl_7.22.0.bb}        |    4 +-
>   10 files changed, 66 insertions(+), 34 deletions(-)
>   rename meta/recipes-core/dropbear/{dropbear-0.52 =>  dropbear-0.53.1}/configure.patch (100%)
>   create mode 100644 meta/recipes-core/dropbear/dropbear/dropbear-0.53.1-static_build_fix.patch
>   delete mode 100644 meta/recipes-core/dropbear/dropbear_0.52.bb
>   create mode 100644 meta/recipes-core/dropbear/dropbear_0.53.1.bb
>   rename meta/recipes-extended/diffutils/{diffutils_3.0.bb =>  diffutils_3.2.bb} (84%)
>   rename meta/recipes-support/curl/{curl_7.21.7.bb =>  curl_7.22.0.bb} (92%)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into master with the md5sum fix by Richard

Thanks
	Sau!




  parent reply	other threads:[~2011-10-05  4:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30  8:16 [PATCH 0/4]Recipe upgrades Mei Lei
2011-09-30  8:16 ` [PATCH 1/4] curl: Upgrade from 7.21.7 to 7.22.0 Mei Lei
2011-09-30 12:23   ` Martin Jansa
2011-09-30 13:40     ` Richard Purdie
2011-09-30  8:16 ` [PATCH 2/4] diffutils: Upgrade from 3.0 to 3.2 Mei Lei
2011-09-30  8:16 ` [PATCH 3/4] dropbear: Upgrade from 0.52 to 0.53.1 Mei Lei
2011-09-30  8:16 ` [PATCH 4/4] distro_tracking_fields.inc: Update upgrade information Mei Lei
2011-10-05  4:10 ` Saul Wold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-11 13:59 [PATCH 0/4] Recipe upgrades Paul Eggleton
2014-01-13 15:22 Paul Eggleton

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=4E8BD89F.70306@intel.com \
    --to=saul.wold@intel.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.