From: Christopher Faylor <cgf@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: MinGW (Was Re: PROPOSAL: Variation on an Alternate policy for obsoleting targets)
Date: Wed, 21 May 2003 03:33:00 -0000 [thread overview]
Message-ID: <20030521032726.GB24962@redhat.com> (raw)
In-Reply-To: <20030520011613.GA629@doctormoo>
On Mon, May 19, 2003 at 09:16:13PM -0400, Nathanael Nerode wrote:
>Patches not getting reviewed in a reasonable amount of time is a known
>problem, and we're all working on it. :-/
Patches that are submitted for mingw which are covered by the parts of
gcc that I maintain are reviewed in a reasonable amount of time.
Patches in other parts of the tree get reviewed as fast as any other
patches get reviewed, AFAICT.
Sometimes mingw/cygwin *bugs* in gnats languish however.
I do what I can. I haven't seen anyone around who was willing to step
in to handle cygwin/mingw issues.
cgf
(windows, cygwin, mingw maintainer)
next prev parent reply other threads:[~2003-05-21 3:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 1:24 Nathanael Nerode
2003-05-21 3:33 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 17:52 MinGW (Was: " Bonzini
2003-05-20 1:16 Stephan T. Lavavej
2003-05-20 4:27 ` Ranjit Mathew
2003-05-20 16:15 ` E. Weddington
2003-05-19 22:40 Stephan T. Lavavej
2003-05-19 23:49 ` Joe Buck
2003-05-20 0:33 ` DJ Delorie
2003-05-21 3:27 ` Christopher Faylor
2003-05-20 4:22 ` Anthony Green
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=20030521032726.GB24962@redhat.com \
--to=cgf@redhat.com \
--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).