From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] devtool/recipetool fixes
Date: Tue, 2 Jul 2019 16:23:58 +1200 [thread overview]
Message-ID: <cover.1562041417.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 1f8a73261c7a134821c40845da27d8edbb0763b6:
Revert "pigz: Add debug for autobuilder errors" (2019-06-30 23:33:12 +0100)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/devtool36-oe
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/devtool36-oe
Paul Eggleton (2):
recipetool: ignore zero-length setup.py files
devtool: upgrade: fix handling of errors parsing upgraded recipe
scripts/lib/devtool/upgrade.py | 28 ++++++++++++-------
.../lib/recipetool/create_buildsys_python.py | 9 ++++--
2 files changed, 25 insertions(+), 12 deletions(-)
--
2.20.1
next reply other threads:[~2019-07-02 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 4:23 Paul Eggleton [this message]
2019-07-02 4:23 ` [PATCH 1/2] recipetool: ignore zero-length setup.py files Paul Eggleton
2019-07-02 4:24 ` [PATCH 2/2] devtool: upgrade: fix handling of errors parsing upgraded recipe 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.1562041417.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