From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/11] Fix missing SUMMARY values
Date: Fri, 6 Nov 2015 15:28:21 +0000 [thread overview]
Message-ID: <cover.1446823542.git.paul.eggleton@linux.intel.com> (raw)
One of my pet peeves is where SUMMARY isn't set properly in a recipe;
we use these in a few places now (packages, the OE layer index,
Toaster, etc.).
The following changes since commit e44ed8c18e395b9c055aefee113b90708e8a8a2f:
build-appliance-image: Update to jethro head revision (2015-11-03 14:02:57 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/summaries
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/summaries
Paul Eggleton (11):
gptfdisk: add SUMMARY
libunwind: add SUMMARY
stress: add SUMMARY
python-nose: add SUMMARY
linux-yocto.inc: set SUMMARY instead of DESCRIPTION
tzcode-native: set SUMMARY instead of DESCRIPTION
alsa-plugins: set SUMMARY instead of DESCRIPTION
swig: set SUMMARY instead of DESCRIPTION
mmc-utils: set SUMMARY instead of DESCRIPTION
gstreamer1.0-meta-base: set SUMMARY instead of DESCRIPTION
texinfo-dummy-native: set SUMMARY instead of DESCRIPTION
meta/recipes-devtools/fdisk/gptfdisk_1.0.0.bb | 1 +
meta/recipes-devtools/mmc/mmc-utils_git.bb | 2 +-
meta/recipes-devtools/python/python-nose_1.3.6.bb | 1 +
meta/recipes-devtools/swig/swig.inc | 2 +-
meta/recipes-extended/stress/stress_1.0.4.bb | 1 +
meta/recipes-extended/texinfo-dummy-native/texinfo-dummy-native.bb | 2 +-
meta/recipes-extended/tzcode/tzcode-native_2015g.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto.inc | 2 +-
meta/recipes-multimedia/alsa/alsa-plugins_1.0.29.bb | 2 +-
meta/recipes-multimedia/gstreamer/gstreamer1.0-meta-base.bb | 2 +-
meta/recipes-support/libunwind/libunwind.inc | 1 +
11 files changed, 11 insertions(+), 7 deletions(-)
--
2.1.0
next reply other threads:[~2015-11-06 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:28 Paul Eggleton [this message]
2015-11-06 15:28 ` [PATCH 01/11] gptfdisk: add SUMMARY Paul Eggleton
2015-11-06 15:28 ` [PATCH 02/11] libunwind: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 03/11] stress: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 04/11] python-nose: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 05/11] linux-yocto.inc: set SUMMARY instead of DESCRIPTION Paul Eggleton
2015-11-06 15:28 ` [PATCH 06/11] tzcode-native: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 07/11] alsa-plugins: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 08/11] swig: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 09/11] mmc-utils: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 10/11] gstreamer1.0-meta-base: " Paul Eggleton
2015-11-06 15:28 ` [PATCH 11/11] texinfo-dummy-native: " 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.1446823542.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