Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7] Recipe cleanups
Date: Tue, 26 Nov 2013 14:41:50 +0000	[thread overview]
Message-ID: <cover.1385476873.git.paul.eggleton@linux.intel.com> (raw)

The following changes since commit 4482af07df26644885bae49b98f5d765a5caa68c:

  qemu: add PACKAGECONFIG for vnc, libcurl, nss, uuid, curses, gtk+, libcap-ng (2013-11-26 12:09:51 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/cleanup
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/cleanup

Paul Eggleton (7):
  squashfs-tools: drop FILESPATHPKG
  squashfs-tools: set SUMMARY instead of DESCRIPTION
  alsa-utils-alsaconf: tidy up path setting
  eee-acpi-scripts: tidy up recipe
  dropbear: set SUMMARY instead of DESCRIPTION
  libpng: set reasonable SUMMARY
  Don't set DESCRIPTION to the same value as SUMMARY

 meta/recipes-bsp/eee-acpi-scripts/eee-acpi-scripts_git.bb | 15 ++++++++-------
 meta/recipes-connectivity/nfs-utils/libnfsidmap_0.25.bb   |  1 -
 meta/recipes-core/dropbear/dropbear.inc                   |  2 +-
 meta/recipes-devtools/cdrtools/cdrtools-native_3.01a17.bb |  1 -
 .../docbook-dsssl-stylesheets-native_1.79.bb              |  1 -
 meta/recipes-devtools/dosfstools/dosfstools_2.11.bb       |  1 -
 .../linuxdoc-tools/linuxdoc-tools-native_0.9.69.bb        |  1 -
 meta/recipes-devtools/qemu/nativesdk-qemu-helper_1.0.bb   |  1 -
 meta/recipes-devtools/sgmlspl/sgmlspl-native_1.03ii.bb    |  1 -
 .../recipes-devtools/squashfs-tools/squashfs-tools_4.2.bb |  5 +----
 meta/recipes-extended/cups/cups.inc                       |  1 -
 meta/recipes-extended/grep/grep_2.15.bb                   |  1 -
 meta/recipes-extended/shadow/shadow-securetty_4.1.4.3.bb  |  1 -
 meta/recipes-extended/shadow/shadow-sysroot_4.1.4.3.bb    |  1 -
 meta/recipes-extended/shadow/shadow.inc                   |  1 -
 meta/recipes-lsb4/libpng/libpng12_1.2.50.bb               |  3 +--
 meta/recipes-lsb4/perl/libdumpvalue-perl_1.17.bb          |  1 -
 .../alsa/alsa-utils-alsaconf_1.0.27.2.bb                  |  3 +--
 meta/recipes-multimedia/libpng/libpng_1.6.6.bb            |  3 +--
 meta/recipes-support/libevent/libevent_2.0.21.bb          |  1 -
 20 files changed, 13 insertions(+), 32 deletions(-)

-- 
1.8.1.2



             reply	other threads:[~2013-11-26 14:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 14:41 Paul Eggleton [this message]
2013-11-26 14:41 ` [PATCH 1/7] squashfs-tools: drop FILESPATHPKG Paul Eggleton
2013-11-26 14:41 ` [PATCH 2/7] squashfs-tools: set SUMMARY instead of DESCRIPTION Paul Eggleton
2013-11-26 14:41 ` [PATCH 3/7] alsa-utils-alsaconf: tidy up path setting Paul Eggleton
2013-11-26 14:41 ` [PATCH 4/7] eee-acpi-scripts: tidy up recipe Paul Eggleton
2013-11-26 14:41 ` [PATCH 5/7] dropbear: set SUMMARY instead of DESCRIPTION Paul Eggleton
2013-11-26 14:41 ` [PATCH 6/7] libpng: set reasonable SUMMARY Paul Eggleton
2013-11-26 14:41 ` [PATCH 7/7] Don't set DESCRIPTION to the same value as 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.1385476873.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