All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Boor <florian.boor@kernelconcepts.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base.bbclass: Use bb.warn instead of bb.error for deprecation notification.
Date: Tue, 03 Feb 2015 13:50:59 +0100	[thread overview]
Message-ID: <54D0C433.50705@kernelconcepts.de> (raw)
In-Reply-To: <CAJTo0LZxw5LV55fi9QA6X=vgM4UrZ-LtHXqp2KuMEVmGffgNiA@mail.gmail.com>

Hi Ross,

On 03.02.2015 13:40, Burton, Ross wrote:
> bb.error is fatal, so it's all good right?

last time I checked (some days ago) it was not necessarily fatal. I was able to
build complete image collecting a pile of PR_INC errors. That's what confused me...
I'll check if I still have the log on another machine later.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de
                                        http://www.kernelconcepts.de/en


  reply	other threads:[~2015-02-03 12:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 10:30 [PATCH] base.bbclass: Use bb.warn instead of bb.error for deprecation notification Florian Boor
2015-02-03 10:43 ` Paul Eggleton
2015-02-03 12:04 ` Otavio Salvador
2015-02-03 12:36   ` Florian Boor
2015-02-03 12:40     ` Burton, Ross
2015-02-03 12:50       ` Florian Boor [this message]
2015-02-03 12:53         ` Otavio Salvador
2015-02-03 13:00           ` Burton, Ross
2015-02-03 13:02             ` Otavio Salvador
2015-02-03 13:20               ` Richard Purdie
2015-02-03 13:24             ` Florian Boor

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=54D0C433.50705@kernelconcepts.de \
    --to=florian.boor@kernelconcepts.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=ross.burton@intel.com \
    /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.