Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Only return parsed configuration files
Date: Tue,  9 Aug 2011 09:23:35 -0700	[thread overview]
Message-ID: <cover.1312906927.git.josh@linux.intel.com> (raw)

This is an updated change to findConfigFilePath which includes review
feedback.

The following changes since commit c3827690b9ba3625d1df32d9517efbe13d7d9a1e:

  bb/ui/hob: Restore toolchain relevant preference settings for build (2011-08-09 15:19:51 +0100)

are available in the git repository at:
  git://github.com/incandescant/bitbake hob
  https://github.com/incandescant/bitbake/tree/hob

Joshua Lock (1):
  bb/cooker: only emit ConfigFilePathFound for files which were parsed

 lib/bb/cooker.py |   28 ++++++++++++++++++++++++++--
 1 files changed, 26 insertions(+), 2 deletions(-)

-- 
1.7.6




             reply	other threads:[~2011-08-09 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 16:23 Joshua Lock [this message]
2011-08-09 16:23 ` [PATCH 1/1] bb/cooker: only emit ConfigFilePathFound for files which were parsed Joshua Lock
2011-08-10 12:38   ` 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=cover.1312906927.git.josh@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=bitbake-devel@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