From: Michael Koch <konqueror@gmx.de>
To: mauve-discuss@sources.redhat.com
Cc: "Shining Liao" <shiningliao@hotmail.com>
Subject: Re: Mauve test case changes
Date: Tue, 07 Dec 2004 16:57:00 -0000 [thread overview]
Message-ID: <200412071750.31395.konqueror@gmx.de> (raw)
In-Reply-To: <BAY2-F7B8401E7189848261C62BB8B50@phx.gbl>
Am Dienstag, 7. Dezember 2004 17:39 schrieb Shining Liao:
> Hi,
> I have downloaded mauve nightly build on 20041117 and 20041207.
> It look to me that there are lots of differences in between. For
> example, All gnu.testlet.java.lang.*
> gnu.testlet.java.math.*
> gnu.testlet.java.net.*
> gnu.testlet.java.security.*
> ... etc.
> test classes are missing!
>
> Where can I get more information about how mauve test cases changed
> and what direction
> are they going to....
I don't know about the tarballs but the best is to use CVS directly:
http://sources.redhat.com/mauve/cvs.html
With CVS you can get diffs between versions and when it was commited
and all such infos.
Michael
--
Homepage: http://www.worldforge.org/
prev parent reply other threads:[~2004-12-07 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 16:40 Shining Liao
2004-12-07 16:57 ` Michael Koch [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=200412071750.31395.konqueror@gmx.de \
--to=konqueror@gmx.de \
--cc=mauve-discuss@sources.redhat.com \
--cc=shiningliao@hotmail.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).