From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] Ensure SUMMARY is set
Date: Wed, 25 May 2016 15:37:08 +1200 [thread overview]
Message-ID: <cover.1464147312.git.paul.eggleton@linux.intel.com> (raw)
SUMMARY should be set in every recipe so you have a reasonable short
description to show in places such as Toaster and devtool search.
The following changes since commit d6241e4c94a0a72acfc57e96a59918c0b2146d65:
useradd: Fix infinite build loop (2016-05-23 10:33:39 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/summary
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/summary
Paul Eggleton (6):
bsd-headers: set SUMMARY instead of DESCRIPTION
fts: set SUMMARY instead of DESCRIPTION
signing-keys: set SUMMARY instead of DESCRIPTION
argp-standalone: set SUMMARY instead of DESCRIPTION
gobject-introspection: set SUMMARY and HOMEPAGE
libjpeg-turbo: set SUMMARY
meta/recipes-core/bsd-headers/bsd-headers.bb | 2 +-
meta/recipes-core/fts/fts.bb | 2 +-
meta/recipes-core/meta/signing-keys.bb | 2 +-
.../gobject-introspection/gobject-introspection_1.46.0.bb | 3 ++-
meta/recipes-graphics/jpeg/libjpeg-turbo_8d+1.4.2.bb | 1 +
meta/recipes-support/argp-standalone/argp-standalone_1.3.bb | 2 +-
6 files changed, 7 insertions(+), 5 deletions(-)
--
2.5.5
next reply other threads:[~2016-05-25 3:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 3:37 Paul Eggleton [this message]
2016-05-25 3:37 ` [PATCH 1/6] bsd-headers: set SUMMARY instead of DESCRIPTION Paul Eggleton
2016-05-25 3:37 ` [PATCH 2/6] fts: " Paul Eggleton
2016-05-25 3:37 ` [PATCH 3/6] signing-keys: " Paul Eggleton
2016-05-25 3:37 ` [PATCH 4/6] argp-standalone: " Paul Eggleton
2016-05-25 3:37 ` [PATCH 5/6] gobject-introspection: set SUMMARY and HOMEPAGE Paul Eggleton
2016-05-25 3:37 ` [PATCH 6/6] libjpeg-turbo: set SUMMARY 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.1464147312.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.