From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [UPGRADES 0/5] upgrade of some of the toolchain recipes
Date: Wed, 25 May 2011 10:18:33 -0700 [thread overview]
Message-ID: <4DDD39E9.6000307@linux.intel.com> (raw)
In-Reply-To: <cover.1306198151.git.nitin.a.kamble@intel.com>
On 05/23/2011 05:50 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>
> The following changes since commit 3504c3a9b1af5a3405e0a03a5ade50b82535b6dd:
>
> documentation/yocto-project-qs/yocto-project-qs.xml: fixed build env script (2011-05-23 15:53:29 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib.git nitin/upgrades
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/upgrades
>
> Nitin A Kamble (5):
> git: upgrade from 1.7.4.3 to 1.7.5.1
> libpcre: upgrade from 8.10 to 8.12
> byacc: upgrade from 20101127 to 20101229
> python-pygpbject: upgrade from 2.27 to 2.27.91
> distro-tracking: update toolchain recipe fields
>
> .../conf/distro/include/distro_tracking_fields.inc | 3 +++
> meta/recipes-devtools/git/files/autotools.patch | 16 ----------------
> meta/recipes-devtools/git/git.inc | 3 +--
> .../git/{git_1.7.4.3.bb => git_1.7.5.1.bb} | 6 +++---
> ...bject_2.27.0.bb => python-pygobject_2.27.91.bb} | 6 +++---
> meta/recipes-extended/byacc/byacc_20101127.bb | 7 -------
> meta/recipes-extended/byacc/byacc_20101229.bb | 7 +++++++
> .../libpcre/{libpcre_8.10.bb => libpcre_8.12.bb} | 6 +++---
> 8 files changed, 20 insertions(+), 34 deletions(-)
> delete mode 100644 meta/recipes-devtools/git/files/autotools.patch
> rename meta/recipes-devtools/git/{git_1.7.4.3.bb => git_1.7.5.1.bb} (56%)
> rename meta/recipes-devtools/python/{python-pygobject_2.27.0.bb => python-pygobject_2.27.91.bb} (87%)
> delete mode 100644 meta/recipes-extended/byacc/byacc_20101127.bb
> create mode 100644 meta/recipes-extended/byacc/byacc_20101229.bb
> rename meta/recipes-support/libpcre/{libpcre_8.10.bb => libpcre_8.12.bb} (94%)
>
Merged into oe-core
Thanks
Sau!
prev parent reply other threads:[~2011-05-25 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 0:50 [UPGRADES 0/5] upgrade of some of the toolchain recipes nitin.a.kamble
2011-05-24 0:50 ` [UPGRADES 1/5] git: upgrade from 1.7.4.3 to 1.7.5.1 nitin.a.kamble
2011-05-24 3:30 ` Saul Wold
2011-05-24 3:31 ` Kamble, Nitin A
2011-05-24 0:50 ` [UPGRADES 2/5] libpcre: upgrade from 8.10 to 8.12 nitin.a.kamble
2011-05-24 0:50 ` [UPGRADES 3/5] byacc: upgrade from 20101127 to 20101229 nitin.a.kamble
2011-05-24 0:50 ` [UPGRADES 4/5] python-pygpbject: upgrade from 2.27 to 2.27.91 nitin.a.kamble
2011-05-24 0:50 ` [UPGRADES 5/5] distro-tracking: update toolchain recipe fields nitin.a.kamble
2011-05-25 17:18 ` Saul Wold [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=4DDD39E9.6000307@linux.intel.com \
--to=sgw@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox