Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [fido][PATCH 00/13] devtool backports for fido (cover letter only)
Date: Fri,  5 Jun 2015 16:03:14 +0100	[thread overview]
Message-ID: <cover.1433516373.git.paul.eggleton@linux.intel.com> (raw)

Some fixes for devtool in fido. The oe-selftest tests all pass with
these applied.

The following changes since commit b266977372f2d5704d00dd07b29ea49898ebf70e:

  combo-layer: handle unset dest_dir in sanity_check() (2015-05-29 13:00:52 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/devtool-fido
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/devtool-fido

Markus Lehtonen (4):
  devtool: call parse_recipe with correct arguments
  devtool: modify: use B=S if that is the default for the recipe
  devtool: modify: implement --no-same-dir
  devtool: include bbappends in recipe parsing

Paul Eggleton (9):
  devtool: handle . in recipe name
  devtool: add: use correct bbappend file name with -V option
  devtool: update-recipe: handle unversioned bbappends
  devtool: update-recipe: check if source tree is a git repository
  recipetool: avoid second-level subdir when extracting
  recipetool: ensure git clone is standalone when extracting
  devtool: fix build env command execution error handling
  devtool: if workspace layer exists, still ensure it's in bblayers.conf
  oe-selftest: devtool: add a proper test to see if tap devices exist

 meta/lib/oe/recipeutils.py        |  10 +--
 meta/lib/oeqa/selftest/devtool.py |  14 ++++-
 scripts/devtool                   |  38 +++++++-----
 scripts/lib/devtool/__init__.py   |   9 ++-
 scripts/lib/devtool/standard.py   | 126 ++++++++++++++++++++++++--------------
 scripts/lib/recipetool/create.py  |  15 +++--
 scripts/lib/scriptutils.py        |  11 ++++
 7 files changed, 148 insertions(+), 75 deletions(-)

-- 
2.1.0



                 reply	other threads:[~2015-06-05 15:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.1433516373.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --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