From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] revised gcc 4.2.3
Date: Fri, 28 Mar 2008 22:16:15 +0000 [thread overview]
Message-ID: <1206742575.3224.108.camel@nigel-x60> (raw)
I modified less things here, how does it look?
I'll rename the 4.2.2 dir to 4.2.3.
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcc-4.2.3.patch
Type: text/x-patch
Size: 11347 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080328/75c0ed86/attachment.bin
-------------- 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/20080328/75c0ed86/attachment.pgp
reply other threads:[~2008-03-28 22:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1206742575.3224.108.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