From: NightStrike <nightstrike@gmail.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
Gerald Pfeifer <gerald@pfeifer.com>,
gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org, NightStrike <nightstrike@gmail.com>
Subject: Re: make install-strip with binutils
Date: Sat, 20 Nov 2010 19:43:00 -0000 [thread overview]
Message-ID: <AANLkTi=0AYDuRDx_KM2BBTx36PW47BjmYYL20sXQjLy=@mail.gmail.com> (raw)
In-Reply-To: <20101120193829.GC24876@gmx.de>
On Sat, Nov 20, 2010 at 2:38 PM, Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> * Gerald Pfeifer wrote on Sat, Nov 20, 2010 at 01:24:13AM CET:
>> On Wed, 17 Nov 2010, Ralf Wildenhues wrote:
>> > Now, as GCC build maintainer, it seems most of this patch is free to
>> > proceed on (still, I'd welcome any review!), and the src bits are
>> > trivial. The web update has been OKed off-list by Gerald, so the only
>> > remaining bits are in gcc/doc/install.texi. Is that part of the build
>> > maintainer role too, or OK to go ahead with?
>>
>> I can approve that one, too. :-)
>>
>> There is one thing there that may confuse our users a bit and that is
>> the following:
>
> Fixed according to your suggestion. Thanks for the review!
This applies to anything in top level configure, right? So we can
install-strip GCC, binutils, gdb, etc?
next prev parent reply other threads:[~2010-11-20 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim3U0h2Orq0k=35f1EH4UDrVuY1aeQMy7V1o9E6@mail.gmail.com>
[not found] ` <20101023095951.GN2183@gmx.de>
[not found] ` <AANLkTiksfrMeF7=U3ie6-vom6arKdc8O0qNkABvYuZAm@mail.gmail.com>
[not found] ` <mcrhbgcub27.fsf@google.com>
[not found] ` <alpine.LFD.2.00.1010240455210.15889@eddie.linux-mips.org>
[not found] ` <20101027182939.GI15343@gmx.de>
[not found] ` <AANLkTikDnZA17jMXbEEX6oLezYKHDm-LZxuXifxdbQCo@mail.gmail.com>
2010-11-02 20:09 ` Ralf Wildenhues
2010-11-17 19:01 ` Ralf Wildenhues
2010-11-20 0:24 ` Gerald Pfeifer
2010-11-20 19:39 ` Ralf Wildenhues
2010-11-20 19:43 ` NightStrike [this message]
2010-11-20 19:46 ` Ralf Wildenhues
2010-11-21 1:28 ` NightStrike
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='AANLkTi=0AYDuRDx_KM2BBTx36PW47BjmYYL20sXQjLy=@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gerald@pfeifer.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