Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Humberto Ibarra <humberto.ibarra.lopez@intel.com>,
	bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v3] bitbake/lib/bb/cookerdata.py: Improve response when bitbake-layers can't find layer conf file
Date: Fri, 13 May 2016 00:10:42 +0100	[thread overview]
Message-ID: <1463094642.9746.58.camel@linuxfoundation.org> (raw)
In-Reply-To: <1463093720.9746.57.camel@linuxfoundation.org>

On Thu, 2016-05-12 at 23:55 +0100, Richard Purdie wrote:
> It would be good to double check as I just tested this with bitbake 
> and bitbake-layers hasn't been ported to python3 yet but I'd imagine 
> its the same.

I just pushed an update to the branch which fixes bitbake-layers under
python3 and confirmed it does show the filename.

Cheers,

Richard



      reply	other threads:[~2016-05-12 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 19:17 [PATCH v3] bitbake/lib/bb/cookerdata.py: Improve response when bitbake-layers can't find layer conf file Humberto Ibarra
2016-05-12 22:55 ` Richard Purdie
2016-05-12 23:10   ` 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=1463094642.9746.58.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=humberto.ibarra.lopez@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox