From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: python 2.6 warning
Date: Tue, 12 May 2009 15:32:20 +0100 [thread overview]
Message-ID: <1242138740.5824.41.camel@ted> (raw)
In-Reply-To: <be7a9f3d0905111711r77d0230eif76b4551d3f05c2c@mail.gmail.com>
On Mon, 2009-05-11 at 21:11 -0300, Otavio Salvador wrote:
> On Mon, May 11, 2009 at 7:37 PM, Richard Purdie <rpurdie@rpsys.net> wrote:
> > I've backported it to bitbake 1.8 and it seems to work along with
> > merging a number of fixes lurking in Poky.
>
> Please push the attached fix too.
Committed, thanks.
(after discussion on irc about why it was needed).
Can people please at least cc the bitbake list on bitbake patches as it
will increase the chances of me seeing them.
Cheers,
Richard
prev parent reply other threads:[~2009-05-12 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 9:22 python 2.6 warning Robert Schuster
2009-05-11 10:10 ` Michael 'Mickey' Lauer
2009-05-11 11:39 ` Philip Balister
2009-05-11 12:54 ` Richard Purdie
2009-05-11 14:19 ` Marcin Juszkiewicz
2009-05-11 22:37 ` Richard Purdie
2009-05-12 0:11 ` Otavio Salvador
2009-05-12 10:54 ` Roman I Khimov
2009-05-12 14:32 ` 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=1242138740.5824.41.camel@ted \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.