From: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] multiple package upgrades
Date: Mon, 27 May 2013 15:19:52 +0300 [thread overview]
Message-ID: <cover.1369657070.git.bogdan.a.marinescu@intel.com> (raw)
Upgrades for git, python-dbus and autogen-native.
The following changes since commit 676fd3f394a0c0576b63c77ed2184bf5f42c29b6:
dropbear: a fix for hang in dropbearkey, built for x32 (2013-05-24 14:14:49 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib bogdanm/work
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bogdanm/work
Bogdan Marinescu (3):
git: upgraded to 1.8.3
python-dbus: upgraded to 1.2.0
autogen-native: upgraded to 5.17.4
...en-native_5.17.3.bb => autogen-native_5.17.4.bb} | 4 ++--
meta/recipes-devtools/autogen/files/guile.patch | 19 +++++++++----------
.../git/{git_1.8.2.2.bb => git_1.8.3.bb} | 4 ++--
.../obsolete_automake_macros.patch | 14 --------------
.../{python-dbus_1.1.1.bb => python-dbus_1.2.0.bb} | 8 +++-----
5 files changed, 16 insertions(+), 33 deletions(-)
rename meta/recipes-devtools/autogen/{autogen-native_5.17.3.bb => autogen-native_5.17.4.bb} (90%)
rename meta/recipes-devtools/git/{git_1.8.2.2.bb => git_1.8.3.bb} (67%)
delete mode 100644 meta/recipes-devtools/python/python-dbus-1.1.1/obsolete_automake_macros.patch
rename meta/recipes-devtools/python/{python-dbus_1.1.1.bb => python-dbus_1.2.0.bb} (70%)
--
1.7.10.4
next reply other threads:[~2013-05-27 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 12:19 Bogdan Marinescu [this message]
2013-05-27 12:19 ` [PATCH 1/3] git: upgraded to 1.8.3 Bogdan Marinescu
2013-05-27 12:19 ` [PATCH 2/3] python-dbus: upgraded to 1.2.0 Bogdan Marinescu
2013-05-27 12:19 ` [PATCH 3/3] autogen-native: upgraded to 5.17.4 Bogdan Marinescu
-- strict thread matches above, loose matches on Subject: below --
2013-06-03 12:56 [PATCH 0/3] multiple package upgrades Bogdan Marinescu
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=cover.1369657070.git.bogdan.a.marinescu@intel.com \
--to=bogdan.a.marinescu@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