public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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:27:00 -0000	[thread overview]
Message-ID: <20030521032244.GA24962@redhat.com> (raw)
In-Reply-To: <200305200008.h4K08vR08264@greed.delorie.com>

On Mon, May 19, 2003 at 08:08:57PM -0400, DJ Delorie wrote:
>>However, there are some platforms which are supported by non-gcc
>>developers and aren't useful as-is from FSF sources, yet the platform's
>>users desperately wish that gcc would work as-is.
>
>The solution to that, is to make those non-gcc developers gcc
>maintainers.
>
>>Given MinGW's importance as the only real way to run gcc on Windows, I
>>don't see why it's not even a secondary platform for gcc.
>
>So make Danny the MinGW maintainer for GCC.

I've been offering this to Danny for some time.  He is not interested.

I'm not sure what the problem is here.  Danny has been pretty good about
getting mingw/cygwin changes into the trunk.  Where possible, I approve
the changes as quickly as possible.  From the MAINTAINERS file:

windows, cygwin, mingw  Christopher Faylor      cgf@redhat.com

The existence of a mingw patch set should not be a cause for alarm.
We're working on getting mingw and cygwin aligned with gcc trunk.  For a
while we had a branch in gcc for development but I dropped that due to
time constraint.  However, the merging of changes from the
patches/branch is happening.  It's just happening in volunteer time,
like most free software projects.

I'm not sure why mingw is being talked about as if it was a secondary
platform.  From my point of view it receives a lot of high quality
attention from Danny.

cgf

  reply	other threads:[~2003-05-21  3:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2003-05-20  4:22 ` Anthony Green
2003-05-20  1:16 Stephan T. Lavavej
2003-05-20  4:27 ` Ranjit Mathew
2003-05-20 16:15 ` E. Weddington
2003-05-20  1:24 MinGW (Was " Nathanael Nerode
2003-05-21  3:33 ` Christopher Faylor
2003-05-20 17:52 MinGW (Was: " Bonzini

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=20030521032244.GA24962@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).