From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Chris Larson <clarson@kergoth.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] u-boot: remove UBOOT_MACHINE and COMPATIBLE_MACHINES
Date: Fri, 27 May 2011 00:24:42 +0100 [thread overview]
Message-ID: <1306452282.27470.214.camel@rex> (raw)
In-Reply-To: <e5f5d48165bcb5dc3ccf160a29e16ca700f85395.1306444161.git.dvhart@linux.intel.com>
On Thu, 2011-05-26 at 14:12 -0700, Darren Hart wrote:
> Note: I used bb.note() instead of bb.debug() to ensure the message at least
> makes it to the console. From what I could gather, bb.debug() doesn't
> go anywhere during recipe parsing.
Why?
We exclude about 30 different recipes when parsing and would you really
want to see a usability message from each one when you likely don't care
about it?
A bb.debug is fine and the user can see it if they run with -D to get
more info. A bb.note is just irritating.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-26 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 21:12 [PATCH v2 0/2] u-boot updates to make it more bbappend friendly Darren Hart
2011-05-26 21:12 ` [PATCH 1/2] u-boot: remove UBOOT_MACHINE and COMPATIBLE_MACHINES Darren Hart
2011-05-26 23:24 ` Richard Purdie [this message]
2011-05-26 23:31 ` Chris Larson
2011-05-27 3:43 ` Darren Hart
2011-05-27 8:40 ` Richard Purdie
2011-05-27 13:56 ` Darren Hart
2011-05-27 14:46 ` Richard Purdie
2011-05-27 14:48 ` Richard Purdie
2011-05-27 15:13 ` Darren Hart
2011-05-27 15:37 ` Richard Purdie
2011-05-26 21:12 ` [PATCH 2/2] u-boot: rename u-boot_git.bb to u-boot_${PV}.bb Darren Hart
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=1306452282.27470.214.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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