From: Tom Tromey <tromey@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Dalibor Topic <robilad@kaffe.org>,
Michael Koch <konqueror@gmx.de>,
Meskauskas Audrius <audriusa@bluewin.ch>,
mauve-discuss@sources.redhat.com
Subject: Re: A place for the Classpath specific tests
Date: Tue, 15 Mar 2005 17:55:00 -0000 [thread overview]
Message-ID: <m33buw23vg.fsf@localhost.localdomain> (raw)
In-Reply-To: <1110908210.1186.53.camel@localhost>
Mark> OK. How about the following patch to the README:
Looks good.
Mark> By having a tag and a special subdirectory for these tests it should be
Mark> simple to enable/disable these special tests for the various ways people
Mark> run mauve (by hand, make, batch_run, ant script, etc).
I think just putting them in a directory named after their class, like
we do for everything, will suffice. Using 'gnu.javax.swing....' is
just as selectable -- and obviously classpath-specific, IMO -- as
'classpath.gnu.javax.swing...'
But I don't have a strong opinion on it.
Tom
prev parent reply other threads:[~2005-03-15 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 14:19 Meskauskas Audrius
2005-03-10 16:07 ` Michael Koch
2005-03-10 16:21 ` Dalibor Topic
2005-03-12 19:24 ` Tom Tromey
2005-03-15 17:37 ` Mark Wielaard
2005-03-15 17:55 ` Tom Tromey [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=m33buw23vg.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=audriusa@bluewin.ch \
--cc=konqueror@gmx.de \
--cc=mark@klomp.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=robilad@kaffe.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).