From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Buildhistory rebuilds fix
Date: Mon, 3 Mar 2014 16:56:49 +0000 [thread overview]
Message-ID: <cover.1393865774.git.paul.eggleton@linux.intel.com> (raw)
The following changes since commit 82c773e88aaefd9321481ad297554d5b4a3ae0b2:
Revert "ncurses: use ln -r to generate relative symlink" (2014-03-03 15:52:26 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-deps2
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildhistory-deps2
Paul Eggleton (2):
bitbake.conf: add new vardepvalueexclude varflag to
BB_SIGNATURE_EXCLUDE_FLAGS
classes/buildhistory: fix task signatures changing
meta/classes/buildhistory.bbclass | 6 ++++--
meta/conf/bitbake.conf | 4 ++--
2 files changed, 6 insertions(+), 4 deletions(-)
--
1.8.5.3
next reply other threads:[~2014-03-03 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 16:56 Paul Eggleton [this message]
2014-03-03 16:56 ` [PATCH 1/2] bitbake.conf: add new vardepvalueexclude varflag to BB_SIGNATURE_EXCLUDE_FLAGS Paul Eggleton
2014-03-03 16:56 ` [PATCH 2/2] classes/buildhistory: fix task signatures changing 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.1393865774.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