From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Matthew McClintock <msm@freescale.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] siggen.py: If both sigs have a variable in it's whitelist then don't say it's changed
Date: Mon, 05 Dec 2011 16:17:55 +0000 [thread overview]
Message-ID: <1323101875.25960.98.camel@ted> (raw)
In-Reply-To: <1322673895-25682-1-git-send-email-msm@freescale.com>
On Wed, 2011-11-30 at 11:24 -0600, Matthew McClintock wrote:
> Some BB_HASHBASE_WHITELIST variables are in the lists of variable
> dependencies for signatures. Ignore those differences in lists
> since this difference does not matter
>
> Signed-off-by: Matthew McClintock <msm@freescale.com>
> ---
> I'm seeing variables in BB_HASHBASE_WHITELIST make it
> to the signature. Not sure if they are used to calculate
> the hash but assuming they are not we don't need to print
> out that they are different
>
> lib/bb/siggen.py | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-12-05 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 17:24 [PATCH] siggen.py: If both sigs have a variable in it's whitelist then don't say it's changed Matthew McClintock
2011-12-05 16:17 ` Richard Purdie [this message]
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=1323101875.25960.98.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=msm@freescale.com \
/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