From: Paolo Bonzini <bonzini@gnu.org>
To: Peter O'Gorman <pogma@thewrittenword.com>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: [PATCH] Update libtool to latest git tip
Date: Mon, 08 Sep 2008 18:30:00 -0000 [thread overview]
Message-ID: <48C56F11.9080606@gnu.org> (raw)
In-Reply-To: <20080908182544.GI19996@localhost.localdomain>
> Well, libtool-2.2.6 is finally released (twice even).
>
>> Actual approval depends on your answer to this question, but the patch is
>> technically okay. Can you commit it to the src repository too? There is
>> some regeneration to do there too.
>
> I know that GCC is now in stage 3, and that we missed the end of stage 1
> by a week, but I would still like to update gcc's libtool to 2.2.6.
It fixed a Darwin bug, right?
Paolo
next prev parent reply other threads:[~2008-09-08 18:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 13:50 libstdc++, gdb and darwin Jack Howarth
2008-08-05 16:32 ` Peter O'Gorman
2008-08-05 21:45 ` Jack Howarth
2008-08-06 16:18 ` Update libtool? (was: Re: libstdc++, gdb and darwin) Peter O'Gorman
2008-08-06 16:20 ` Jack Howarth
2008-08-06 16:27 ` Update libtool? Peter O'Gorman
2008-08-06 18:45 ` Ralf Wildenhues
2008-08-06 18:53 ` Peter O'Gorman
2008-08-07 6:53 ` Paolo Bonzini
2008-08-07 7:39 ` Paolo Bonzini
2008-08-07 17:29 ` Peter O'Gorman
2008-08-11 20:02 ` Ralf Wildenhues
2008-08-11 20:03 ` Peter O'Gorman
2008-08-21 5:36 ` [PATCH] Update libtool to latest git tip (was: Re: Update libtool?) Peter O'Gorman
2008-08-21 14:46 ` [PATCH] Update libtool to latest git tip Paolo Bonzini
2008-09-08 18:27 ` Peter O'Gorman
2008-09-08 18:30 ` Paolo Bonzini [this message]
2008-09-08 19:09 ` Peter O'Gorman
2008-09-08 20:39 ` Paolo Bonzini
2008-10-03 23:17 ` libstdc++, gdb and darwin Jack Howarth
2008-10-04 1:30 ` Peter O'Gorman
2008-10-04 2:26 ` Jack Howarth
2008-10-04 4:55 ` Peter O'Gorman
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=48C56F11.9080606@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=pogma@thewrittenword.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).