All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/4] Fixes for variable dependency handling with contains functions
Date: Mon,  3 Apr 2017 11:19:02 +1200	[thread overview]
Message-ID: <cover.1491175014.git.paul.eggleton@linux.intel.com> (raw)

Fixes for a few issues I discovered while working on bitbake-diffsigs.

The following changes since commit 58a03531c8183b165bb7dcad86d8559c92bc150d:

  fetch2: Do not fail to create symbolic links if they already exist (2017-04-01 08:23:29 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib paule/bb-contains
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-contains

Paul Eggleton (4):
  lib/bb/data: fix dependency handling for contains and multiple values
  codeparser: improve handling of contains_any() and filter()
  bitbake-selftest: add contains tests
  codeparser: add some comments

 lib/bb/cache.py            |  2 +-
 lib/bb/codeparser.py       | 34 +++++++++++++++++++++++++++++---
 lib/bb/data.py             | 10 ++++++----
 lib/bb/tests/codeparser.py | 48 ++++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 86 insertions(+), 8 deletions(-)

-- 
2.9.3



             reply	other threads:[~2017-04-02 23:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-02 23:19 Paul Eggleton [this message]
2017-04-02 23:19 ` [PATCH 1/4] lib/bb/data: fix dependency handling for contains and multiple values Paul Eggleton
2017-04-02 23:19 ` [PATCH 2/4] codeparser: improve handling of contains_any() and filter() Paul Eggleton
2017-04-02 23:19 ` [PATCH 3/4] bitbake-selftest: add contains tests Paul Eggleton
2017-04-02 23:19 ` [PATCH 4/4] codeparser: add some comments 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.1491175014.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@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 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.