From: Rob Savoye <rob@welcomehome.org>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Fernando Nasser <fnasser@redhat.com>,
Michael Elizabeth Chastain <mec@shout.net>,
drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: RFC: KFAIL DejaGnu patch
Date: Tue, 09 Apr 2002 07:38:00 -0000 [thread overview]
Message-ID: <20020409084535.A11086@welcomehome.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020409105157.10632D-100000@is>; from Eli Zaretskii on Tue, Apr 09, 2002 at 10:56:21AM +0300
On Tue, Apr 09, 2002 at 10:56:21AM +0300, Eli Zaretskii wrote:
> What good is it to have documentation one is unable to modify?
"Unable to modify" ? I think you mean unwilling. People modify the DejaGnu
manual without problem all the time. Docbook looks alot like HTML... It's
easy to modify, produces better output, and used by many GNU projects.
I realize texinfo is the standard format for the GNU project, but then
again, I'm not supposed to be using Tcl either. :-) Seriously, considering
the quality of most of the engineers I've known on the GDB team, learning
what little one would know to update a docbook manual is trivial.
> So please reconsider the possibility of going back to Texinfo. Since I
As an engineer, I've gone through several documentation formats over the
last 24 years. Nroff, man pages, texinfo, and now docbook. I'm far from
an expert on documentation formats, but I only switched after many,
many meetings about this back when we started eCOS. Even Cygnus's
own doc team prefered Docbook. (I don't know about RedHats's) Anyway,
I see no reason to go backwards. Sorry. If you have to, send me manual
updates as text, and I'll merge them in. 99& of the time, nobody ever
updates the doc but me anyway. I prefer Docbook, once I got used to it.
I haven't been able to get docbook2texi to fully work yet anyway...
- rob -
next prev parent reply other threads:[~2002-04-09 14:38 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
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 [this message]
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=20020409084535.A11086@welcomehome.org \
--to=rob@welcomehome.org \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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