From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86
Date: Fri, 21 Mar 2008 17:32:38 +0000 [thread overview]
Message-ID: <1206120758.2562.114.camel@nigel-x60> (raw)
In-Reply-To: <46a136670803211029i22e0c783j5c24db2a229a1c9e@mail.gmail.com>
> I noticed, looking through that patch, there are lots of little
> changes that affect the code path for all arches. That can't be good,
> or right. Also, there are huge chunks of unchanged code that probably
> got white-spaced somehow and don't even belong in there. I truly am
> sorry for unleashing that mess on you guys. I'm cranking away at
> finding a stable fix, along with bugging the Atmel guys about it. I
> think Atmel Norway must be on holiday or something, because they've
> been awfully quiet lately.
After about 10 million pgdwn's in the patch I kinda gave up ... some
pretty nasty changes they've made, I agree!
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080321/5a8688e0/attachment.pgp
prev parent reply other threads:[~2008-03-21 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 11:21 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86 ninevoltz at uclibc.org
2008-03-21 11:39 ` Peter Korsgaard
2008-03-21 11:55 ` John Voltz
2008-03-21 15:14 ` Thiago A. Corrêa
2008-03-21 15:24 ` John Voltz
2008-03-21 15:33 ` Thiago A. Corrêa
2008-03-21 15:44 ` John Voltz
[not found] ` <47E3D9E4.6000901@apss.it>
2008-03-21 16:31 ` John Voltz
2008-03-22 2:11 ` Thiago A. Corrêa
2008-03-25 22:58 ` [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1:avr32_patches_break_x86 Ulf Samuelsson
2008-03-21 17:21 ` [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86 Nigel Kukard
2008-03-21 17:23 ` John Voltz
2008-03-21 17:29 ` John Voltz
2008-03-21 17:32 ` Nigel Kukard [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=1206120758.2562.114.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--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