From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Matthew McClintock <msm@freescale.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] siggen.py: sort task hash depedencies with basepath
Date: Wed, 23 Nov 2011 17:49:44 +0000 [thread overview]
Message-ID: <1322070584.15626.18.camel@ted> (raw)
In-Reply-To: <1322035440-8480-1-git-send-email-msm@freescale.com>
On Wed, 2011-11-23 at 02:04 -0600, Matthew McClintock wrote:
> Without this patch the tash hash dependencies can be in a order
> that is dependent upon directory/filesystem layout. With this
> change the data is sorted the same regardless.
>
> Without this the dependent hashes could be in different orders
> on different systems and consequently final md5 hash would differ
> as well even though nothing else changed.
>
> Signed-off-by: Matthew McClintock <msm@freescale.com>
> ---
> lib/bb/siggen.py | 25 ++++++++++++++-----------
> 1 files changed, 14 insertions(+), 11 deletions(-)
Merged to master, thanks!
Richard
prev parent reply other threads:[~2011-11-23 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 8:04 [PATCH] siggen.py: sort task hash depedencies with basepath Matthew McClintock
2011-11-23 17:49 ` 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=1322070584.15626.18.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 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.