From: Paolo Bonzini <bonzini@gnu.org>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH 5/N] post-update cleanups
Date: Sat, 15 Aug 2009 16:58:00 -0000 [thread overview]
Message-ID: <4A86E930.6040406@gnu.org> (raw)
In-Reply-To: <20090815113449.GE20172@gmx.de>
The GCC bits are fine by me. It will likely take a few days until we
finish discussing the details of override.m4 and testing the src/
directories, and this will give enough time to the binutils and gdb
folks to look at the patch & scream.
Thanks again!
Paolo
next prev parent reply other threads:[~2009-08-15 16:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 11:29 Moving to Autoconf 2.64, Automake 1.11 Ralf Wildenhues
2009-08-15 11:31 ` [PATCH 1/N] Update automake-provided files in the toplevel Ralf Wildenhues
2009-08-15 11:33 ` [PATCH 3/N] some minor fixes in sim, gold, gdb Ralf Wildenhues
2009-08-17 16:17 ` Tom Tromey
2009-08-17 16:19 ` Ian Lance Taylor
2009-08-15 11:34 ` Moving to Autoconf 2.64, Automake 1.11 Gerald Pfeifer
2009-08-16 9:49 ` Do not point to sources.redhat.com for autotools tarballs (was: Moving to Autoconf 2.64, Automake 1.11) Ralf Wildenhues
2009-08-16 17:23 ` Eli Zaretskii
2009-08-15 11:34 ` [PATCH 4/N] The big bump Ralf Wildenhues
2009-08-15 11:49 ` Richard Guenther
2009-08-15 12:23 ` Ralf Wildenhues
2009-08-15 12:29 ` Ralf Wildenhues
2009-08-15 16:21 ` Paolo Bonzini
2009-08-17 20:47 ` fix 2.64 fopen glitch, disable option checking (was: [PATCH 4/N] The big bump) Ralf Wildenhues
2009-08-17 22:52 ` fix 2.64 fopen glitch, disable option checking Paolo Bonzini
2009-08-15 14:41 ` [PATCH 4/N] The big bump Dave Korn
2009-08-15 16:04 ` Ralf Wildenhues
2009-08-15 16:36 ` Dave Korn
[not found] ` <20090818191404.GB30961__32944.9385325008$1250622877$gmane$org@gmx.de>
2009-08-18 20:32 ` Tom Tromey
2009-08-24 17:31 ` Christopher Faylor
2009-08-24 19:17 ` updating autotools in the rest of src (was: [PATCH 4/N] The big bump) Ralf Wildenhues
2009-08-15 16:26 ` [PATCH 4/N] The big bump Joseph S. Myers
2009-08-18 19:36 ` Ralf Wildenhues
2009-08-18 19:40 ` Paolo Bonzini
2009-08-19 0:00 ` Dave Korn
2009-08-17 11:49 ` Nick Clifton
2009-08-18 18:18 ` Ralf Wildenhues
2009-08-19 7:07 ` Nick Clifton
2009-08-23 13:24 ` Andreas Schwab
2009-08-23 13:31 ` yacc and lex reruns without maintainer-mode (was: [PATCH 4/N] The big bump) Ralf Wildenhues
2009-08-24 7:18 ` Alan Modra
2009-08-15 11:35 ` [PATCH 5/N] post-update cleanups Ralf Wildenhues
2009-08-15 16:58 ` Paolo Bonzini [this message]
2009-08-15 15:31 ` Moving to Autoconf 2.64, Automake 1.11 Joseph S. Myers
2009-08-15 16:07 ` Ralf Wildenhues
2009-08-16 11:48 ` install-{html,pdf} (was: Moving to Autoconf 2.64, Automake 1.11) Ralf Wildenhues
2009-08-17 12:12 ` install-{html,pdf} Paolo Bonzini
2009-08-15 18:04 ` Moving to Autoconf 2.64, Automake 1.11 Paolo Bonzini
2009-08-15 23:07 ` Ralf Wildenhues
[not found] ` <20090815113449.GE20172__4676.41973305053$1250336143$gmane$org@gmx.de>
2009-08-17 16:19 ` [PATCH 5/N] post-update cleanups Tom Tromey
2009-08-23 9:44 ` Moving to Autoconf 2.64, Automake 1.11 Ralf Wildenhues
2009-08-27 14:23 ` Matthias Klose
2009-08-27 15:02 ` Matthias Klose
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=4A86E930.6040406@gnu.org \
--to=bonzini@gnu.org \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).