public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/14344] [3.3.3 Regression] MinGW Bootstrap Failure Date: Sun, 29 Feb 2004 23:41:00 -0000 [thread overview] Message-ID: <20040229234116.3027.qmail@sources.redhat.com> (raw) In-Reply-To: <20040229144929.14344.stl@caltech.edu> ------- Additional Comments From gdr at integrable-solutions dot net 2004-02-29 23:41 ------- Subject: Re: [3.3.3 Regression] MinGW Bootstrap Failure "cgf at redhat dot com" <gcc-bugzilla@gcc.gnu.org> writes: | >| I'm beginning to think this should be in the FAQ or something... | > | >I like FAQs, but in this case I don't know what it would be about, for | >you're claiming something which contradicts what Danny just said. | | I was representing what Danny had repeatedly asserted whenever I | asked him about this. He's since changed his mind, apparently. | | I have no problem whatsoever with adding him to the maintainership for | mingw/cygwin. It's past due, IMO. Great! I'm going to make the suggestion to SC, saying you're OK with that. Thanks! -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14344
next prev parent reply other threads:[~2004-02-29 23:41 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-29 14:49 [Bug bootstrap/14344] New: " stl at caltech dot edu 2004-02-29 16:20 ` [Bug bootstrap/14344] " gdr at integrable-solutions dot net 2004-02-29 16:23 ` [Bug target/14344] " pinskia at gcc dot gnu dot org 2004-02-29 16:23 ` pinskia at gcc dot gnu dot org 2004-02-29 16:56 ` stl at caltech dot edu 2004-02-29 17:09 ` gdr at integrable-solutions dot net 2004-02-29 18:58 ` stl at caltech dot edu 2004-02-29 19:33 ` gdr at integrable-solutions dot net 2004-02-29 19:45 ` stl at caltech dot edu 2004-02-29 19:55 ` pinskia at gcc dot gnu dot org 2004-02-29 20:00 ` stl at caltech dot edu 2004-02-29 20:04 ` gdr at integrable-solutions dot net 2004-02-29 20:08 ` gdr at integrable-solutions dot net 2004-02-29 20:10 ` dannysmith at gcc dot gnu dot org 2004-02-29 20:18 ` gdr at integrable-solutions dot net 2004-02-29 20:31 ` stl at caltech dot edu 2004-02-29 20:53 ` dannysmith at gcc dot gnu dot org 2004-02-29 21:04 ` stl at caltech dot edu 2004-02-29 21:39 ` stl at caltech dot edu 2004-02-29 21:57 ` cgf at redhat dot com 2004-02-29 22:03 ` stl at caltech dot edu 2004-02-29 22:29 ` cgf at redhat dot com 2004-02-29 22:44 ` gdr at integrable-solutions dot net 2004-02-29 22:48 ` cgf at redhat dot com 2004-02-29 22:57 ` gdr at integrable-solutions dot net 2004-02-29 23:36 ` cgf at redhat dot com 2004-02-29 23:41 ` gdr at integrable-solutions dot net [this message] 2004-02-29 23:50 ` Christopher Faylor 2004-02-29 23:57 ` stl at caltech dot edu
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=20040229234116.3027.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).