From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mei Lei <lei.mei@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/5]libffi,psmisc,e2fsprogs,libidn upgrade
Date: Mon, 18 Apr 2011 11:02:23 +0100 [thread overview]
Message-ID: <1303120943.5518.92.camel@rex> (raw)
In-Reply-To: <cover.1302856115.git.lei.mei@intel.com>
On Sat, 2011-01-15 at 22:22 +0800, Mei Lei wrote:
> This pull request contain 4 recipes upgrade, please help to review it and pull.
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: lmei3/upgrade-0413
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=lmei3/upgrade-0413
>
> Thanks,
> Mei Lei <lei.mei@intel.com>
> ---
>
>
> Mei Lei (5):
> libidn: upgrade from 1.19 to 1.20
> e2fsprogs: Upgrade from 1.41.12 to 1.41.14
> psmisc: Upgrade from 22.2 to 22.13
I merged these thanks.
> libffi: Upgrade from 3.0.9 to 3.0.10rc0
However this is an upgrade to an rc release. We should wait for the
3.0.10 stable release before we upgrade unless there is a pressing
reason to do otherwise.
> distro_tracking_fields.inc: update e2fsprogs,libidn,libffi,psmisc
> information
I didn't take this as I didn't take the libffi update above.
Cheers,
Richard
prev parent reply other threads:[~2011-04-18 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 14:18 [PATCH 0/5]libffi,psmisc,e2fsprogs,libidn upgrade Mei Lei
2011-04-15 14:17 ` [PATCH 1/5] libidn: upgrade from 1.19 to 1.20 Mei Lei
2011-04-15 14:17 ` [PATCH 2/5] e2fsprogs: Upgrade from 1.41.12 to 1.41.14 Mei Lei
2011-04-15 14:18 ` [PATCH 3/5] psmisc: Upgrade from 22.2 to 22.13 Mei Lei
2011-04-15 14:18 ` [PATCH 4/5] libffi: Upgrade from 3.0.9 to 3.0.10rc0 Mei Lei
2011-04-15 14:18 ` [PATCH 5/5] distro_tracking_fields.inc: update e2fsprogs, libidn, libffi, psmisc information Mei Lei
2011-04-18 10:02 ` 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=1303120943.5518.92.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=lei.mei@intel.com \
--cc=poky@yoctoproject.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