From: Danny Smith <dannysmith@clear.net.nz>
To: gcc@gcc.gnu.org
Subject: Re: mh-mingw32
Date: Thu, 09 Dec 2004 07:46:00 -0000 [thread overview]
Message-ID: <001501c4ddc2$a7d032d0$926d65da@DANNY> (raw)
http://gcc.gnu.org/ml/gcc/2004-12/msg00309.html
From: Christopher Faylor
>On Wed, Dec 08, 2004 at 03:36:38PM +0000, Joern RENNECKE wrote:
>> Why does config/mh-mingw32 clear LIBGCC2_DEBUG_CFLAGS ? Debugging
>> information in the target libgcc of a mingw32 hosted cross tool chain
>> is quite useful.
> From the CVS logs, it looks like this predates my tenure as windows
> maintainer by several years. It is probably a historical artifact.
> Unless Danny Smith objects, I'd say feel free to nuke that line.
No objections from me. If you nuke that line, you may as well nuke the
whole file.
Danny
> cgf
next reply other threads:[~2004-12-09 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 7:46 Danny Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 15:36 mh-mingw32 Joern RENNECKE
2004-12-08 16:08 ` mh-mingw32 Christopher Faylor
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='001501c4ddc2$a7d032d0$926d65da@DANNY' \
--to=dannysmith@clear.net.nz \
--cc=dannysmith@users.sourceforge.net \
--cc=gcc@gcc.gnu.org \
/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).