From: tom.zanussi@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] python: fix missing PR bump
Date: Wed, 9 Nov 2011 09:11:58 -0600 [thread overview]
Message-ID: <cover.1320851307.git.tom.zanussi@intel.com> (raw)
From: Tom Zanussi <tom.zanussi@intel.com>
Simple one-liner adding the missing PR bump for my previous python commit.
Thanks to Koen Kooi for pointing it out...
The following changes since commit 23d2eaf9d283cae47e52d1151f0d4ad53bbbe8a0:
Tom Zanussi (1):
python: skip setup.py 'import check' when cross-compiling
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib.git tzanussi/python-pr-bump
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/python-pr-bump
Tom Zanussi (1):
python: bump PR
meta/recipes-devtools/python/python_2.7.2.bb | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2011-11-09 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 15:11 tom.zanussi [this message]
2011-11-09 15:12 ` [PATCH 1/1] python: bump PR tom.zanussi
2011-11-10 17:25 ` [PATCH 0/1] python: fix missing PR bump Saul Wold
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.1320851307.git.tom.zanussi@intel.com \
--to=tom.zanussi@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