All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: [PATCH 0/1 V2] bitbake-whatchanged: print what is about to happen
Date: Fri, 10 Aug 2012 11:47:38 +0800	[thread overview]
Message-ID: <cover.1344569166.git.liezhi.yang@windriver.com> (raw)

Changes of V2:

* Fix a typo fn -> 'fn'

* Use "bitbake -e" rather than "bitbake -e recipe" to get the BB_STAMPS_DIR

* Use "BB_STAMPS_DIR=<path> bitbake -S recipe" to regenerate the stamps

* Change the summary format a little, now it looks like:
  - (without -v):
    === Summary: (3653 changed, 1927 unchanged)
    Newly added: 807
    PV changed: 48
    PR changed: 276
    Depends changed: 2522

  - (with -v):
    === Summary: (3653 changed, 1927 unchanged)
    Newly added: 807
    Depends changed: 2846

// Robert

The following changes since commit 2dec760b79bb7e2e79c33c5127fa64685bd86a18:

  foomatic: fix perl path for target (2012-08-08 10:06:00 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib robert/whatchanged
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/whatchanged

Robert Yang (1):
  bitbake-whatchanged: print what is about to happen

 bitbake/bin/bitbake-whatchanged | 328 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 328 insertions(+)
 create mode 100755 bitbake/bin/bitbake-whatchanged

-- 
1.7.11.2




             reply	other threads:[~2012-08-10  3:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  3:47 Robert Yang [this message]
2012-08-10  3:47 ` [PATCH 1/1 V2] bitbake-whatchanged: print what is about to happen Robert Yang
2012-08-10 13:38   ` Chris Larson
2012-08-11  3:38     ` Robert Yang
2012-08-10 14:28 ` [PATCH 0/1 " Paul Eggleton
2012-08-11  2:05   ` Robert Yang
2012-08-11  3:10     ` Robert Yang

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.1344569166.git.liezhi.yang@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=bitbake-devel@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.