From: Mark Wielaard <mark@klomp.org>
To: Noa Resare <noa@resare.com>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: [PATCH] xml output from mauve (updated)
Date: Sun, 19 Sep 2004 21:51:00 -0000 [thread overview]
Message-ID: <1095630709.1284.65.camel@localhost.localdomain> (raw)
In-Reply-To: <1095540446.2660.48.camel@c-351f72d5.01-60-6c6b701.cust.bredbandsbolaget.se>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi,
On Sat, 2004-09-18 at 22:47, Noa Resare wrote:
> On fre, 2004-09-17 at 23:20 +0200, Noa Resare wrote:
> > So, I did some afternoon hacking and came up with this patch to mauve
> > that outputs the results from a mauve run into an xml file for easy
> > parsing. I haven't written anything that does anything with the output
> > yet but I thought I could share this with you anyway.
>
> This updated patch handles mauve output containing & < and > properly.
> It also adds Makefile.am to the changelog entry.
>
> ps. a test result diff program (that looks for regressions) in very
> rough form is available from http://resare.com/noa/testdiff
Very nice!
Maybe this should be written as a new XMLTestHarness class?
Although I don't really see a problem with just tagging it on the
SimpleTestHarness. Opinions anybody?
Are you sure the XML escaping is always correct?
Maybe it doesn't really matter in this case, but you might want to look
whether GNU Kawa (http://www.gnu.org/software/kawa/) has something
appropriate in the gnu.xml package.
Thanks for doing this. Having easy to compare mauve results is very
valuable.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-19 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 21:20 [PATCH] xml output from mauve Noa Resare
2004-09-18 20:47 ` [PATCH] xml output from mauve (updated) Noa Resare
2004-09-19 21:51 ` Mark Wielaard [this message]
2004-09-20 6:48 ` Noa Resare
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=1095630709.1284.65.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=noa@resare.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).