All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] recipeutils fixes for devtool
Date: Thu, 29 Nov 2018 10:55:25 +1300	[thread overview]
Message-ID: <3617389.9Irff3jv64@localhost.localdomain> (raw)
In-Reply-To: <cover.1543378296.git.paul.eggleton@linux.intel.com>

On Wednesday, 28 November 2018 5:16:13 PM NZDT Paul Eggleton wrote:
> A couple of fixes for issues in the recipeutils module (which affect
> devtool), a cleanup patch, and some additional related tests for
> oe-selftest.

Oops, patch 4/4 missed out the actual meta-selftest recipes that a few of the 
tests rely upon. Branch re-pushed and v2 of 4/4 sent.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




      parent reply	other threads:[~2018-11-28 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28  4:16 [PATCH 0/4] recipeutils fixes for devtool Paul Eggleton
2018-11-28  4:16 ` [PATCH 1/4] lib/oe/recipeutils: patch_recipe(): fix handling of values across includes/classes Paul Eggleton
2018-11-28  4:16 ` [PATCH 2/4] lib/oe/recipeutils: patch_recipe(): fix replacing varflag values Paul Eggleton
2018-11-28  4:16 ` [PATCH 3/4] lib/oe/recipeutils: drop obsolete functions Paul Eggleton
2018-11-28  4:16 ` [PATCH 4/4] oe-selftest: add some tests for recipeutils module Paul Eggleton
2018-11-28 21:54   ` [PATCH v2 " Paul Eggleton
2018-11-29  9:21     ` [PATCH v3 " Paul Eggleton
2018-11-29 14:06       ` Richard Purdie
2018-11-29 19:35         ` Paul Eggleton
2018-11-29 23:09           ` richard.purdie
2018-11-29 23:41             ` Paul Eggleton
2018-11-29 23:38       ` [PATCH v4 " Paul Eggleton
2018-11-28 21:55 ` Paul Eggleton [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=3617389.9Irff3jv64@localhost.localdomain \
    --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 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.