From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] scripts/sstate-diff.sh: add simple script to compare sstate checksums between MACHINEs
Date: Tue, 04 Dec 2012 13:03:00 +0000 [thread overview]
Message-ID: <1354626180.25268.47.camel@ted> (raw)
In-Reply-To: <1354622874-4038-1-git-send-email-Martin.Jansa@gmail.com>
On Tue, 2012-12-04 at 13:07 +0100, Martin Jansa wrote:
> * takes tmpdir, machines and targets from command arguments or env variables
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> scripts/sstate-diff.sh | 107 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 107 insertions(+)
> create mode 100755 scripts/sstate-diff.sh
>
> diff --git a/scripts/sstate-diff.sh b/scripts/sstate-diff.sh
Can we call this something a little more intuitive like
sstate-diff-machines ?
Cheers,
Richard
next prev parent reply other threads:[~2012-12-04 13:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 16:51 [RFC 0/5] OPTDEFAULTTUNE for arm tune files Martin Jansa
2012-09-22 16:51 ` [RFC 1/5] arch-arm: add ARMPKGSFX_CPU to TUNE_PKGARCH because we're using different TUNE_CCARGS Martin Jansa
2012-09-22 16:51 ` [RFC 2/5] tune-xscale, tune-arm926ejs: add OPTDEFAULTTUNE variable and use more generic DEFAULTTUNE as default Martin Jansa
2012-09-22 17:45 ` Richard Purdie
2012-09-27 8:37 ` Martin Jansa
2012-09-27 18:58 ` Mark Hatle
2012-09-27 19:12 ` Martin Jansa
2012-09-27 19:18 ` Mark Hatle
2012-09-27 19:40 ` Martin Jansa
2012-09-27 19:53 ` Mark Hatle
2012-09-27 20:16 ` Martin Jansa
2012-09-28 11:02 ` Phil Blundell
2012-09-28 18:21 ` Martin Jansa
2012-10-02 18:43 ` Martin Jansa
2012-10-02 20:36 ` Mark Hatle
2012-10-02 20:38 ` Martin Jansa
2012-10-02 20:47 ` Mark Hatle
2012-09-22 16:51 ` [RFC 3/5] optimized-tune.inc: add optional distro include Martin Jansa
2012-09-22 16:51 ` [RFC 4/5] bitbake.conf: add TUNE_CCARGS[vardepvalue] Martin Jansa
2012-09-22 16:51 ` [RFC 5/5] tune-xscale, tune-arm926ejs: drop ARMPKGSFX_CPU, change ARMPKGARCH instead Martin Jansa
2012-10-04 13:23 ` [PATCH 0/7] conf/machine: fix arm tune files Martin Jansa
2012-10-04 13:23 ` [PATCH 1/7] tune-xscale: replace TUNE_CCARGS for webkit-gtk and cairo only with xscale in TUNE_FEATURES Martin Jansa
2012-10-04 16:55 ` Khem Raj
2012-10-04 17:13 ` Martin Jansa
2012-10-04 13:23 ` [PATCH 2/7] bitbake.conf: add TUNE_CCARGS[vardepvalue] Martin Jansa
2012-10-04 13:23 ` [PATCH 3/7] tune-cortexr4: fix march value Martin Jansa
2012-10-04 16:55 ` Khem Raj
2012-10-04 13:23 ` [PATCH 4/7] arm/arch-arm*: define ARMPKGARCH_tune-* for default tunes Martin Jansa
2012-10-04 13:23 ` [PATCH 5/7] arch-arm: define different ARMPKGARCH when different CCARGS are used Martin Jansa
2012-10-04 13:23 ` [PATCH 6/7] tune-*: define more generic DEFAULTTUNE to share feed between machines Martin Jansa
2012-10-04 13:23 ` [PATCH 7/7] scripts/sstate-diff.sh: add simple script to compare sstate checksums between MACHINEs Martin Jansa
2012-12-04 12:07 ` [PATCHv2] " Martin Jansa
2012-12-04 13:03 ` Richard Purdie [this message]
2012-12-04 15:24 ` [PATCHv3] " Martin Jansa
2012-12-04 15:26 ` [PATCHv4] scripts/sstate-diff-machines.sh: " Martin Jansa
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=1354626180.25268.47.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.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