From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] scripts/buildenv-internal/sanity: Update to python 2.7.3 as a minimum
Date: Fri, 07 Jun 2013 18:22:42 +0100 [thread overview]
Message-ID: <1370625762.6864.67.camel@ted> (raw)
In-Reply-To: <1370625553.6864.64.camel@ted>
On Fri, 2013-06-07 at 18:19 +0100, Richard Purdie wrote:
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I should add that I'm aware that some of these commit messages are
missing full explaintions. I will add those before they get merged, I
just ran out of time today yet wanted to post them for others to see.
Its pretty clear what the patches are doing and why is covered in other
emails I've written today.
This series does depend on the bitbake series which I've posted to
bitbake-devel.
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/t8
is the series (ignore the top two commits).
Cheers,
Richard
prev parent reply other threads:[~2013-06-07 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 17:19 [PATCH] scripts/buildenv-internal/sanity: Update to python 2.7.3 as a minimum Richard Purdie
2013-06-07 17:22 ` 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=1370625762.6864.67.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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