From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Ensure gcc family recipes having same sstate hash
Date: Fri, 10 Feb 2012 07:58:09 -0800 [thread overview]
Message-ID: <4F353E91.4010904@linux.intel.com> (raw)
In-Reply-To: <cover.1328845545.git.lianhao.lu@intel.com>
On 02/09/2012 07:47 PM, Lianhao Lu wrote:
> Ensure the gcc family recipes having the same sstate hash for do_patch task,
> because they share the same source directory.
>
> The following changes since commit 4ef5e70f531f48cef90805402c16ec02ad3f2b92:
> Christopher Larson (1):
> tcmode-default: add preference for gdb/gdbserver
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib llu/gccfix
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/gccfix
>
> Lianhao Lu (1):
> gcc: Ensure same sstate hashes for shared soruce directory
>
> meta/recipes-devtools/gcc/gcc-common.inc | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-core
Thanks
Sau!
prev parent reply other threads:[~2012-02-10 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 3:47 [PATCH 0/1] Ensure gcc family recipes having same sstate hash Lianhao Lu
2012-02-10 3:47 ` [PATCH 1/1] gcc: Ensure same sstate hashes for shared soruce directory Lianhao Lu
2012-02-10 15:58 ` Saul Wold [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=4F353E91.4010904@linux.intel.com \
--to=sgw@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