From: David Gilbert <david.gilbert@object-refinery.com>
To: Thomas Fitzsimmons <fitzsim@redhat.com>
Cc: mauve-patches@sources.redhat.com
Subject: Re: RFC: remove old harness
Date: Fri, 09 Jun 2006 15:48:00 -0000 [thread overview]
Message-ID: <4489987D.8000403@object-refinery.com> (raw)
In-Reply-To: <4486E4A2.50004@redhat.com>
Thomas Fitzsimmons wrote:
> Hi,
>
> This patch removes the old harness and makes the new one the default.
> It also makes:
>
> ./configure --with-vm=/path/to/vm
> make
> make check
>
> work. I wanted some comments before making this change. It reports
> test results differently -- each test is a pass/fail rather than each
> check -- so we'll also need to update our nightly scripts.
>
> The new harness is better than the old one in every way, in my
> opinion, so I see no reason in keeping the old one around.
>
> What do people think?
>
> Tom
No objections from me.
Regards,
Dave
next prev parent reply other threads:[~2006-06-09 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 14:39 Thomas Fitzsimmons
2006-06-09 15:48 ` David Gilbert [this message]
2006-06-12 15:44 ` Tom Tromey
2006-06-14 19:30 ` Anthony Balkissoon
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=4489987D.8000403@object-refinery.com \
--to=david.gilbert@object-refinery.com \
--cc=fitzsim@redhat.com \
--cc=mauve-patches@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).