All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] gcc 4.2.2 patch
Date: Fri, 28 Mar 2008 20:22:02 +0000	[thread overview]
Message-ID: <1206735722.3224.70.camel@nigel-x60> (raw)

Is this patch ok to bump gcc to 4.2.2?

I grep -r'd the buildroot tree and replaced each occurrence manually and
removed 4.2.0.

-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcc-4.2.2.patch
Type: text/x-patch
Size: 18843 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080328/5c11163b/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/5c11163b/attachment.pgp 

             reply	other threads:[~2008-03-28 20:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 20:22 Nigel Kukard [this message]
2008-03-28 20:41 ` [Buildroot] gcc 4.2.2 patch Bernhard Fischer
2008-03-28 20:59   ` Peter Korsgaard
2008-03-28 21:10     ` Bernhard Fischer
2008-03-28 21:16       ` Nigel Kukard
2008-03-28 21:03   ` Nigel Kukard
2008-03-28 21:13     ` Bernhard Fischer

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=1206735722.3224.70.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.