From: Bill Bartley <bbartley@nowonder.com>
To: help-gcc@gnu.org
Subject: Re: MINGW32
Date: Sat, 27 Nov 1999 21:59:00 -0000 [thread overview]
Message-ID: <3840C375.387D43A5@nowonder.com> (raw)
In-Reply-To: <81cacv$mjm$1@news.doit.wisc.edu>
Perhaps that first link should be " http://sourceware.cygnus.com/ml/ " ?
Bill
Mumit Khan wrote:
>
> Mingw32 questions are probably best posted to the appropriate mailing
> lists -
>
> - Cygwin -- http://sourceware.cygnus.com/lists.html ) -- Mingw and Cygwin
> share the same development tools, so the answers are the same.
> - Mingw32 -- http://www.eGroups.COM/lists/mingw32.html
>
> Regards,
> Mumit
WARNING: multiple messages have this Message-ID
From: Bill Bartley <bbartley@nowonder.com>
To: help-gcc@gnu.org
Subject: Re: MINGW32
Date: Tue, 30 Nov 1999 23:28:00 -0000 [thread overview]
Message-ID: <3840C375.387D43A5@nowonder.com> (raw)
Message-ID: <19991130232800.0IUi5TqOCDBBIu5IEyGqcLnqZeSXmHGGlQTV_KeJvvc@z> (raw)
In-Reply-To: <81cacv$mjm$1@news.doit.wisc.edu>
Perhaps that first link should be " http://sourceware.cygnus.com/ml/ " ?
Bill
Mumit Khan wrote:
>
> Mingw32 questions are probably best posted to the appropriate mailing
> lists -
>
> - Cygwin -- http://sourceware.cygnus.com/lists.html ) -- Mingw and Cygwin
> share the same development tools, so the answers are the same.
> - Mingw32 -- http://www.eGroups.COM/lists/mingw32.html
>
> Regards,
> Mumit
next prev parent reply other threads:[~1999-11-27 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-22 12:10 MINGW32 Uri Yanover
1999-11-22 13:07 ` MINGW32 Mumit Khan
1999-11-23 12:30 ` MINGW32 Uri Yanover
1999-11-30 23:28 ` MINGW32 Uri Yanover
1999-11-27 21:59 ` Bill Bartley [this message]
1999-11-28 11:45 ` MINGW32 Mumit Khan
1999-11-30 23:28 ` MINGW32 Mumit Khan
1999-11-30 23:28 ` MINGW32 Bill Bartley
1999-11-30 23:28 ` MINGW32 Mumit Khan
1999-11-30 23:28 ` MINGW32 Uri Yanover
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=3840C375.387D43A5@nowonder.com \
--to=bbartley@nowonder.com \
--cc=help-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).