From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] sstate-cache-management.sh: look in meta* above oe-core dir when looking for available tunes
Date: Sun, 02 Sep 2012 13:07:53 +0100 [thread overview]
Message-ID: <3830362.NxTCTzAyLx@helios> (raw)
In-Reply-To: <bc9cba103446ace4d9158470cdccd58801a66978.1346584261.git.Martin.Jansa@gmail.com>
On Sunday 02 September 2012 13:13:20 Martin Jansa wrote:
> * many layouts have other layers on the same level as oe-core checkout
This is beginning to indicate that this script really needs to actually know
something about your configuration rather than trying to guess it.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-02 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 11:13 [PATCH 0/4] sstate-cache-management.sh fixes [YOCTO #2897] Martin Jansa
2012-09-02 11:13 ` [PATCH 1/4] sstate-cache-management.sh: fix regexp in checksum grep Martin Jansa
2012-09-02 11:13 ` [PATCH 2/4] sstate-cache-management.sh: fix regexp in AVAILTUNES grep Martin Jansa
2012-09-02 11:13 ` [PATCH 3/4] sstate-cache-management.sh: look in meta* above oe-core dir when looking for available tunes Martin Jansa
2012-09-02 12:07 ` Paul Eggleton [this message]
2012-09-03 7:23 ` Martin Jansa
2012-09-03 7:49 ` Paul Eggleton
2012-09-02 11:13 ` [PATCH 4/4] sstate-cache-management.sh: don't hardcode available machines only to qemu* Martin Jansa
[not found] ` <cover.1346684630.git.Martin.Jansa@gmail.com>
2012-09-03 15:05 ` [PATCH 5/9] sstate-cache-management.sh: add option to enable debug output Martin Jansa
2012-09-04 14:53 ` Saul Wold
2012-09-03 15:05 ` [PATCH 6/9] sstate-cache-management.sh: fix remove_duplicated when multiple archs were built Martin Jansa
2012-09-04 12:42 ` [PATCH 0/4] sstate-cache-management.sh fixes [YOCTO #2897] Richard Purdie
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=3830362.NxTCTzAyLx@helios \
--to=paul.eggleton@linux.intel.com \
--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 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.