From: Fernando Nasser <fnasser@redhat.com>
To: Rob Savoye <rob@welcomehome.org>
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
Michael Elizabeth Chastain <mec@shout.net>,
ac131313@cygnus.com, drow@mvista.com,
gdb-patches@sources.redhat.com
Subject: Re: RFC: KFAIL DejaGnu patch
Date: Mon, 08 Apr 2002 08:52:00 -0000 [thread overview]
Message-ID: <3CB1B784.7391CD4E@redhat.com> (raw)
In-Reply-To: <20020408093125.B3523@welcomehome.org>
Rob Savoye wrote:
>
> On Mon, Apr 08, 2002 at 08:58:52AM +0300, Eli Zaretskii wrote:
>
> > Are there any reason not to continue maintaining the document in
> > Texinfo? Especially since the latest makeinfo supports DocBook (as well
> > as HTML and XML)?
>
> The main reason is that texinfo formatted version is way out of date,
> because I stopped maintaining it when I converted the whole thing by hand
> to SGML/DocBook several years ago. I guess the main problem is that DocBook
> doesn't spit out an info page, which would be kindof nice... But there has
> been alot added to the sgml formatted version that would all have to be
> merged back into the texinfo document.
>
> btw - Matt says he'll add the extra fields for ERROR and WARNING to the
> XML output, which he's hoping will be done as soon as he firms up the DTD.
> Anything else you need to have that be useful ?
>
The KFAIL/KPASS will be there, right?
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2002-04-08 15:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 9:53 RFC: KFAILs [Was: [RFA/mi-testsuite] XFAIL mi*-console.exp] Michael Elizabeth Chastain
2002-04-05 10:22 ` Daniel Jacobowitz
2002-04-05 13:45 ` Andrew Cagney
2002-04-05 13:51 ` Daniel Jacobowitz
2002-04-05 10:23 ` Fernando Nasser
2002-04-05 16:32 ` RFC: KFAIL DejaGnu patch Fernando Nasser
2002-04-05 17:05 ` Andrew Cagney
2002-04-07 16:25 ` Rob Savoye
2002-04-05 17:10 ` Daniel Jacobowitz
2002-04-05 17:40 ` Andrew Cagney
2002-04-08 8:37 ` Fernando Nasser
2002-04-07 16:29 ` Rob Savoye
2002-04-07 22:05 ` Eli Zaretskii
2002-04-08 8:22 ` Rob Savoye
2002-04-08 8:52 ` Fernando Nasser [this message]
2002-04-08 9:01 ` Rob Savoye
2002-04-08 8:41 ` Fernando Nasser
2002-04-08 9:00 ` Rob Savoye
2002-04-08 13:55 ` Andrew Cagney
2002-04-08 16:21 ` Rob Savoye
2002-04-08 16:34 ` Andrew Cagney
2002-04-08 16:48 ` Rob Savoye
2002-04-08 16:58 ` Andrew Cagney
2002-04-08 17:09 ` Rob Savoye
2002-04-08 23:58 ` Eli Zaretskii
2002-04-09 7:38 ` Rob Savoye
2002-04-08 23:53 ` Eli Zaretskii
2002-04-09 7:06 ` Daniel Jacobowitz
2002-04-05 16:51 Michael Elizabeth Chastain
2002-04-05 17:57 Michael Elizabeth Chastain
2002-04-06 14:40 Michael Elizabeth Chastain
2002-04-07 9:10 Michael Elizabeth Chastain
2002-04-07 18:41 Michael Elizabeth Chastain
2002-04-08 9:57 Michael Elizabeth Chastain
2002-04-08 10:34 Michael Elizabeth Chastain
2002-04-08 11:38 ` Daniel Jacobowitz
2002-04-09 7:50 ` Rob Savoye
2002-04-08 11:56 Michael Elizabeth Chastain
2002-04-09 9:13 Michael Elizabeth Chastain
2002-04-09 9:34 ` Rob Savoye
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=3CB1B784.7391CD4E@redhat.com \
--to=fnasser@redhat.com \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
--cc=rob@welcomehome.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