From: Brian Jones <cbj@gnu.org>
To: tromey@redhat.com
Cc: Adam Megacz <gcj@lists.megacz.com>, java@gcc.gnu.org
Subject: Re: apologies, 3.1, mingw wishlist
Date: Tue, 09 Apr 2002 17:50:00 -0000 [thread overview]
Message-ID: <m38z7wl7sa.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <87pu18ebws.fsf@creche.redhat.com>
Tom Tromey <tromey@redhat.com> writes:
> Adam> - Get the testsuite to run (somehow -- not sure yet how I'll do it)
>
> AG suggests using Wine. Anything that works is fine by me though.
If you have to, running Mauve under cygwin shouldn't be too difficult.
Brian
--
Brian Jones <cbj@gnu.org>
next prev parent reply other threads:[~2002-04-10 0:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 15:29 Adam Megacz
2002-04-09 15:36 ` Tom Tromey
2002-04-09 17:50 ` Brian Jones [this message]
2002-04-11 10:57 ` Adam King
2002-04-11 12:52 ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz
2002-04-11 15:20 ` Tom Tromey
2002-04-11 15:53 ` Java debugger Adam King
2002-04-11 17:28 ` Nic Ferrier
2002-04-11 17:36 ` Bryce McKinlay
2002-04-11 23:13 ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz
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=m38z7wl7sa.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=gcj@lists.megacz.com \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.com \
/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).