From: Peter Seebach <peter.seebach@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Chris Larson <clarson@kergoth.com>, bitbake-devel@lists.openembedded.org
Subject: Re: v2 [PATCH 0/2] data_smart.py: Track inclusions and assignments
Date: Tue, 22 May 2012 11:13:59 -0500 [thread overview]
Message-ID: <20120522111359.54be2700@wrlaptop> (raw)
In-Reply-To: <1337694219.8248.6.camel@ted>
On Tue, 22 May 2012 14:43:39 +0100
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> So I want to take a closer look through the patches but I'm leaning
> toward merging them. If we find ways to make things neater, great but
> this is probably as good a start as we can hope for.
They need one small bug fixed (there's a missing [1] in the mods to
createCopy), but apart from that I'm using them without noticeable
trouble.
If these get added to bitbake, there's a related change to oe-core
that might be handy, to suppress sanity checks when using this feature
so you can get an explanation of what went wrong.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2012-05-22 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:10 v2 [PATCH 0/2] data_smart.py: Track inclusions and assignments Peter Seebach
2012-05-21 15:10 ` [PATCH 1/2] data_smart.py: Provide (optional) logging of variable modifications Peter Seebach
2012-05-21 15:10 ` [PATCH 2/2] data_smart.py: Track configuration file inclusions Peter Seebach
2012-05-21 19:54 ` v2 [PATCH 0/2] data_smart.py: Track inclusions and assignments Chris Larson
2012-05-21 20:26 ` Peter Seebach
2012-05-22 13:43 ` Richard Purdie
2012-05-22 16:13 ` Peter Seebach [this message]
2012-05-25 6:56 ` Richard Purdie
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=20120522111359.54be2700@wrlaptop \
--to=peter.seebach@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=richard.purdie@linuxfoundation.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