From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Buildhistory fixes
Date: Wed, 11 Jul 2018 16:56:48 +0200 [thread overview]
Message-ID: <cover.1531320900.git.paul.eggleton@linux.intel.com> (raw)
Fixes for a couple of buildhistory bugs in YP bugzilla plus one extra
that I found in the process.
The following changes since commit f9324af88a99eca28b160fa31aa4516fd397e44b:
distutils3: pass build arguments when doing a clean (2018-07-10 11:10:14 +0100)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-fixes2
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/buildhistory-fixes2
Paul Eggleton (3):
lib/oe/buildhistory_analysis: drop related field feature
classes/buildhistory: handle packaged files with names containing
spaces
classes/buildhistory: properly process escaped chars from pkgdata
meta/classes/buildhistory.bbclass | 5 ++--
meta/lib/oe/buildhistory_analysis.py | 42 ++++++++--------------------
2 files changed, 15 insertions(+), 32 deletions(-)
--
2.17.1
next reply other threads:[~2018-07-11 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 14:56 Paul Eggleton [this message]
2018-07-11 14:56 ` [PATCH 1/3] lib/oe/buildhistory_analysis: drop related field feature Paul Eggleton
2018-07-11 14:56 ` [PATCH 2/3] classes/buildhistory: handle packaged files with names containing spaces Paul Eggleton
2018-07-11 14:56 ` [PATCH 3/3] classes/buildhistory: properly process escaped chars from pkgdata Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 5:02 [PATCH 0/3] Buildhistory fixes 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.1531320900.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 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.