From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] Packaging / warning fixes
Date: Fri, 17 Apr 2015 16:43:06 +0100 [thread overview]
Message-ID: <cover.1429285210.git.paul.eggleton@linux.intel.com> (raw)
A few fixes for things that have been bugging me lately. (I realise
we've just changed the S warning recently, hopefully this is the last
time...)
Changes since v1:
* Adjust message for installed-vs-shipped to suggest not installing
* Add S warning improvement patch
The following changes since commit cfc43743b0e41cf168cad9cbd4e9d870b8f01f03:
toolchain-scripts: Allow the CONFIGSITE_CACHE variable to be overridden (2015-04-15 14:29:54 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/pkgfixes
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/pkgfixes
Paul Eggleton (3):
classes/package: clarify installed-vs-shipped message
lib/oe/package_manager: avoid traceback with no packages
classes/base: clarify S not set correctly warning
meta/classes/base.bbclass | 2 +-
meta/classes/package.bbclass | 3 ++-
meta/lib/oe/package_manager.py | 2 ++
3 files changed, 5 insertions(+), 2 deletions(-)
--
2.1.0
next reply other threads:[~2015-04-17 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 15:43 Paul Eggleton [this message]
2015-04-17 15:43 ` [PATCH v2 1/3] classes/package: clarify installed-vs-shipped message Paul Eggleton
2015-04-17 15:43 ` [PATCH v2 2/3] lib/oe/package_manager: avoid traceback with no packages Paul Eggleton
2015-04-17 15:43 ` [PATCH v2 3/3] classes/base: clarify S not set correctly warning 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.1429285210.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