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/8] buildhistory improvements
Date: Wed, 26 Aug 2015 15:17:12 +0100	[thread overview]
Message-ID: <cover.1440598330.git.paul.eggleton@linux.intel.com> (raw)

A set of improvements for the buildhistory class: 
* A fix for not pushing after making "No changes" commits
* Four fixes for the recently added package file listing functionality
* A patch to avoid errors if additional files are added at the recipe
  level in extension classes
* A couple of patches improving the commit messages


The following changes since commit f07045fcae859c902434062d1725f1348f42d1dd:

  oeqa/oetest.py: add better package search for hasPackage() (2015-08-26 08:26:37 +0100)

are available in the git repository at:

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

Paul Eggleton (8):
  classes/buildhistory: ensure we push when "no changes" commits are made
  classes/buildhistory: exclude . in file listings
  classes/buildhistory: indent recently added function consistently
  classes/buildhistory: tweak buildhistory_list_pkg_files
  classes/buildhistory: fix permissions in package file listing
  classes/buildhistory: handle additional files at recipe level
  classes/buildhistory: include metadata revisions in commit message
  classes/buildhistory: add build result to commit message

 meta/classes/buildhistory.bbclass | 95 ++++++++++++++++++++++++++++-----------
 1 file changed, 70 insertions(+), 25 deletions(-)

-- 
2.1.0



             reply	other threads:[~2015-08-26 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 14:17 Paul Eggleton [this message]
2015-08-26 14:17 ` [PATCH 1/8] classes/buildhistory: ensure we push when "no changes" commits are made Paul Eggleton
2015-08-26 14:17 ` [PATCH 2/8] classes/buildhistory: exclude . in file listings Paul Eggleton
2015-08-26 14:17 ` [PATCH 3/8] classes/buildhistory: indent recently added function consistently Paul Eggleton
2015-08-26 14:17 ` [PATCH 4/8] classes/buildhistory: tweak buildhistory_list_pkg_files Paul Eggleton
2015-08-26 14:17 ` [PATCH 5/8] classes/buildhistory: fix permissions in package file listing Paul Eggleton
2015-08-26 14:17 ` [PATCH 6/8] classes/buildhistory: handle additional files at recipe level Paul Eggleton
2015-08-26 14:17 ` [PATCH 7/8] classes/buildhistory: include metadata revisions in commit message Paul Eggleton
2015-08-26 14:17 ` [PATCH 8/8] classes/buildhistory: add build result to " 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.1440598330.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