From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Fwd: Re: svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86]
Date: Fri, 21 Mar 2008 17:30:59 +0000 [thread overview]
Message-ID: <1206120659.2562.111.camel@nigel-x60> (raw)
Argh ... would it be ok to set the default ML reply-to as the ML? or an
insane proposition from my side? ;)
-N
-------- Forwarded Message --------
> From: Nigel Kukard <nkukard@lbsd.net>
> To: John Voltz <john.voltz@gmail.com>
> Subject: Re: [Buildroot] svn commit:
> trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86
> Date: Fri, 21 Mar 2008 17:29:19 +0000
>
> > ftp://at91dist:distrib at 81.80.104.162/AT91_Third_Party_Design_Flow/Linux_Host/Source
>
> Swell ... thanks!
>
> However they look like the same ones in buildroot :( ... not sure how
> far back the corruption goes. I think pre-Oct '07 patchset was working
> when I last tested.
>
> -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/efe4adcb/attachment.pgp
next reply other threads:[~2008-03-21 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 17:30 Nigel Kukard [this message]
2008-03-21 18:38 ` [Buildroot] reply-to munging (was) [Fwd: Re: svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86] JS
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=1206120659.2562.111.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