Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] package.bbclass: convert unpackaged file message from 'info' to 'warn' so that it shows up on the console
Date: Mon, 09 May 2011 10:48:28 +0100	[thread overview]
Message-ID: <1304934508.30391.195.camel@rex> (raw)
In-Reply-To: <1304787012.8459.1.camel@doubt>

On Sat, 2011-05-07 at 09:50 -0700, Darren Hart wrote:
> According to my discussion with RP, bb.note() is supposed to appear on
> the console. If it doesn't, that is a bug in bitbake, not the recipe
> logging. I used this information to document the intended use of the
> similarly named bbnote() in logging.bbclass.

What we said was that bb.note from "core" context appears on the
console, bb.note from task context does not as it makes the default
console too verbose.

I'm in agreement that unpackaged files should be a warning.

Cheers,

Richard




  parent reply	other threads:[~2011-05-09  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 14:48 [PATCH] package.bbclass: convert unpackaged file message from 'info' to 'warn' so that it shows up on the console Koen Kooi
2011-05-06 14:57 ` Mark Hatle
2011-05-06 15:19 ` Tom Rini
2011-05-07 16:50 ` Darren Hart
2011-05-08  6:23   ` Khem Raj
2011-05-09  7:11     ` Koen Kooi
2011-05-09  7:16       ` Graeme Gregory
2011-05-09  9:48   ` Richard Purdie [this message]
2011-05-09 16:06 ` 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=1304934508.30391.195.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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