Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/9] devtool fixes
Date: Mon, 27 Apr 2015 10:53:12 +0100	[thread overview]
Message-ID: <cover.1430128109.git.paul.eggleton@linux.intel.com> (raw)

This series rolls up some patches previously posted by Markus (with
very minor tweaks to a couple of the commit messages), and adds some
additional patches from me.

Changes since v1:
* Drop "devtool: extract: remove patches when S=WORKDIR" as it needs
  further work
* Replace Markus's oe-selftest fix with a rewritten one which avoids
  almost any dependency on the number/name of patches within the
  mtd-utils recipe (since a recent change just broke the old test
  again)
* Add a couple of fixes for update-recipe
* Touch up a couple of the commit messages


The following changes since commit 46869abf72c1c5babce49537f221d7a4f53ca820:

  oeqa/selftest/toaster: fix bad indent (2015-04-27 10:09:55 +0100)

are available in the git repository at:

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

Markus Lehtonen (3):
  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 (6):
  oe-selftest: devtool: fix test_devtool_update_recipe_git
  devtool: handle . in recipe name
  devtool: add: use correct bbappend file name with -V option
  devtool: reset: avoid errors in case file no longer exists
  devtool: update-recipe: handle unversioned bbappends
  devtool: update-recipe: check if source tree is a git repository

 meta/lib/oe/recipeutils.py        |  10 ++--
 meta/lib/oeqa/selftest/devtool.py |  30 +++++++-----
 scripts/devtool                   |   2 +-
 scripts/lib/devtool/standard.py   | 100 +++++++++++++++++++++++++-------------
 4 files changed, 92 insertions(+), 50 deletions(-)

-- 
2.1.0



             reply	other threads:[~2015-04-27  9:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  9:53 Paul Eggleton [this message]
2015-04-27  9:53 ` [PATCH v2 1/9] devtool: modify: use B=S if that is the default for the recipe Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 2/9] devtool: modify: implement --no-same-dir Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 3/9] oe-selftest: devtool: fix test_devtool_update_recipe_git Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 4/9] devtool: include bbappends in recipe parsing Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 5/9] devtool: handle . in recipe name Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 6/9] devtool: add: use correct bbappend file name with -V option Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 7/9] devtool: reset: avoid errors in case file no longer exists Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 8/9] devtool: update-recipe: handle unversioned bbappends Paul Eggleton
2015-04-27  9:53 ` [PATCH v2 9/9] devtool: update-recipe: check if source tree is a git repository Paul Eggleton

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.1430128109.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