All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] PR bumps to allow removal of meta-oe bbappends
Date: Tue, 16 Apr 2013 16:25:06 +0100	[thread overview]
Message-ID: <cover.1366125772.git.paul.eggleton@linux.intel.com> (raw)

If we can apply these for 1.4 we can drop the bbappends in meta-oe,
which should avoid unnecessary rebuilds when adding that layer.

Since v1, bump by 2 as originally requested by Martin and bump INC_PR
for the qt4-* recipes as pointed out by him in feedback.


The following changes since commit 1a70a3225947aa45f3e1f377d50a5865aac64d2b:

  runqemu-internal: Drop distcc support (2013-04-16 12:39:27 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/qt-meta-oe-bbappends
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qt-meta-oe-bbappends

Paul Eggleton (3):
  packagegroup-qte-toolchain-target: bump PR to allow removal of
    meta-oe bbappend
  qt4-embedded: bump PR to allow removal of meta-oe bbappend
  qt4-x11-free: bump PR to allow removal of meta-oe bbappend

 meta/recipes-qt/packagegroups/packagegroup-qte-toolchain-target.bb |    2 +-
 meta/recipes-qt/qt4/qt4-embedded.inc                               |    2 +-
 meta/recipes-qt/qt4/qt4-x11-free.inc                               |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

-- 
1.7.10.4




             reply	other threads:[~2013-04-16 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 15:25 Paul Eggleton [this message]
2013-04-16 15:25 ` [PATCH v2 1/3] packagegroup-qte-toolchain-target: bump PR to allow removal of meta-oe bbappend Paul Eggleton
2013-04-16 15:25 ` [PATCH v2 2/3] qt4-embedded: " Paul Eggleton
2013-04-16 15:25 ` [PATCH v2 3/3] qt4-x11-free: " 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.1366125772.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.