From: Phil Blundell <philb@gnu.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-configure-cross: factor out --enable-threads argument into ${GCCTHREADS}
Date: Wed, 26 Sep 2012 11:28:01 +0100 [thread overview]
Message-ID: <1348655282.31293.94.camel@phil-desktop> (raw)
In-Reply-To: <20120926100123.GF3313@jama.jama.net>
On Wed, 2012-09-26 at 12:01 +0200, Martin Jansa wrote:
> Sorry I haven't noticed that it's the same value as before.
>
> But if it causes different sstate checksum than PR bump would be nice to get new
> builddir (well maybe not needed after f15f61af77cc4e52a037f509f8e49e1ea530cf35).
OK. In that case I'll leave the patch alone for now and see if Richard
will swallow it as it stands.
p.
next prev parent reply other threads:[~2012-09-26 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 9:45 [PATCH] gcc-configure-cross: factor out --enable-threads argument into ${GCCTHREADS} Phil Blundell
2012-09-26 9:54 ` Martin Jansa
2012-09-26 9:57 ` Phil Blundell
2012-09-26 10:01 ` Martin Jansa
2012-09-26 10:28 ` Phil Blundell [this message]
2012-09-26 13:46 ` Richard Purdie
2012-09-26 10:46 ` Henning Heinold
2012-09-26 10:50 ` Phil Blundell
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=1348655282.31293.94.camel@phil-desktop \
--to=philb@gnu.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