Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Mon, 20 Dec 1999 13:19:25 -0500 To: Mumit Khan Cc: mingw32@egroups.com, cygwin users Subject: Re: [mingw32] Re: ANNOUNCE selfhosting mingw32 Message-ID: <19991220131925.A1316@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Mumit Khan , mingw32@egroups.com, cygwin users References: <19991220120426.A1058@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from khan@NanoTech.Wisc.EDU on Mon, Dec 20, 1999 at 11:56:17AM -0600 On Mon, Dec 20, 1999 at 11:56:17AM -0600, Mumit Khan wrote: >On Mon, 20 Dec 1999, Chris Faylor wrote: >> Out of curiousity, would it help if I had Cygnus sponsor a mingw mailing >> list? I've thought about this from time to time but since the two >> projects were sort of linked, I never took action. Now that there is a >> mingw which does not rely on cygwin, I am thinking that enforcing a >> distinction between the two projects makes sense. > >Actually, Mingw hasn't "depended" on Cygwin for years now, either for >building (I've built all the releases under Unix) or running. They're >still linked of course due to the common backends used by the compiler >and especially binutils. I must confess ignorance of the fact that there was a separate mingw mailing list. If I had known I probably would have suggested moving people there who had mingw questions. I understand that it is sometimes somewhat difficult to draw a line between the two but I'm going to be more sensitive to this in the future now that I know about this. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com