From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.3.2
Date: Thu, 05 Feb 2009 15:04:19 +0100 [thread overview]
Message-ID: <87iqnpaskc.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1233840852.6323.7.camel@sven> (Sven Neumann's message of "Thu\, 05 Feb 2009 14\:34\:12 +0100")
>>>>> "Sven" == Sven Neumann <s.neumann@phase-zero.de> writes:
Sven> Hi,
Sven> That is actually a slightly different patch than what was applied
Sven> upstream in the gcc-4.3 branch, see
Sven> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39076
Sven> Both approaches are discussed here:
Sven> http://gcc.gnu.org/ml/gcc-patches/2008-04/msg01577.html
I don't see any conclusion in that mail, but I'll fix it if your patch
is what got committed upstream.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-05 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 13:24 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.3.2 jacmet at uclibc.org
2009-02-05 13:34 ` Sven Neumann
2009-02-05 14:04 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 14:13 jacmet at uclibc.org
2009-02-05 13:24 jacmet at uclibc.org
2009-01-30 10:35 jacmet at uclibc.org
2009-01-23 23:03 ulf at uclibc.org
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=87iqnpaskc.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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