From: Eli Zaretskii <eliz@is.elta.co.il>
To: Rob Savoye <rob@welcomehome.org>
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: Mon, 08 Apr 2002 23:58:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020409105157.10632D-100000@is> (raw)
In-Reply-To: <20020408181754.I21238@welcomehome.org>
On Mon, 8 Apr 2002, Rob Savoye wrote:
> The entire DejaGnu community is way larger than
> just the GCC/GDB/Binutils team... and some of those other developers also
> know Docbook... While I think the various GCC/GDB people spread around the
> world are likely the most active DejaGnu users, as long as they can *read*
> the documentation in whatever output format they prefer, they're happy.
What good is it to have documentation one is unable to modify?
It took (and still takes) a lot of effort to help developers master
Texinfo (try searching this list for comments to various docs patches, if
you want examples). I hope that slowly people here are beginning to
realize that accompaining code changes with corresponding doco changes is
not such a hard requirement after all. This is a good development, I
think. If we add yet another language to what people need to know, we
might simply ruin it all.
So please reconsider the possibility of going back to Texinfo. Since I
understand there's a tool available to make the conversion, it sounds
like the amount of work is not large.
next prev parent reply other threads:[~2002-04-09 6:58 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 [this message]
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=Pine.SUN.3.91.1020409105157.10632D-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=fnasser@redhat.com \
--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