From: "C. Brian Jones" <cbj@gnu.org>
To: Michael Fletcher <mike.fletcher@theplanet.ca>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Mauve Distributable
Date: Wed, 16 Jun 2004 23:04:00 -0000 [thread overview]
Message-ID: <1087427047.2563.1.camel@lyta.haphazard.org> (raw)
In-Reply-To: <40CB6D97.3050604@theplanet.ca>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Sat, 2004-06-12 at 16:54, Michael Fletcher wrote:
> Hello.
>
> I would like to hack the makefiles so that they could produced a
> distributable mauve test suite. I would like this so that it would be
> easier for someone to test there VM's against Mauve. For example one
> might only need to run:
>
> java -jar mauve-jdk1.4.jar
> sablevm-java -jar mauve-jdk1.4.jar
> kaffe-java -jar mauve-jdk1.4.jar
>
> This would also make it easier to run the test suite under Windows.
I'm interested in the same thing. No time to work on it now. Main
concern expressed before is to ensure gcj's testsuite continues to work
after making changes.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-06-16 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 20:59 Michael Fletcher
2004-06-16 23:04 ` C. Brian Jones [this message]
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=1087427047.2563.1.camel@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=mike.fletcher@theplanet.ca \
/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).