From: graydon hoare <graydon@redhat.com>
To: mauve-discuss@sources.redhat.com
Subject: Re: JUnit integration
Date: Thu, 27 Nov 2003 20:14:00 -0000 [thread overview]
Message-ID: <87vfp5fu4d.fsf@dub.venge.net> (raw)
In-Reply-To: <87fzg9r5nu.fsf@fleche.redhat.com>
Tom Tromey <tromey@redhat.com> writes:
> First, different VMs use Classpath differently...
> Second, traditionally Mauve hasn't required any copyright assignments..
> Third, it is useful to be able to run Mauve against non-Classpath..
ah well, it was worth a passing thought :)
-graydon
prev parent reply other threads:[~2003-11-27 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 2:51 graydon hoare
2003-11-27 4:34 ` Classpath / Mauve integration Stephen Crawley
2003-11-27 10:29 ` JUnit integration Raif S. Naffah
2003-11-27 19:17 ` Tom Tromey
2003-11-27 20:14 ` graydon hoare [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=87vfp5fu4d.fsf@dub.venge.net \
--to=graydon@redhat.com \
--cc=mauve-discuss@sources.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).