Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rob Savoye <rob@welcomehome.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: 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 16:48:00 -0000	[thread overview]
Message-ID: <20020408175713.D21238@welcomehome.org> (raw)
In-Reply-To: <3CB22901.7000700@cygnus.com>; from Andrew Cagney on Mon, Apr 08, 2002 at 07:34:25PM -0400

On Mon, Apr 08, 2002 at 07:34:25PM -0400, Andrew Cagney wrote:

> Why?  Is there a posting somewhere explaining the rationale for this?
 
  I'll have to look around. Mark Gallassi at that time had alot of good
info on this, as he was Cygnus's DocTools maintainer. (btw, the page on
sourceware is way out of date) Briefly though, the main reasons we chose
it for eCOS, and the Linux Doc project choose it is Docbook is an 
international used standard for technical documentation. Framemaker
suports it, CISCO, and many other companies use it for technical
documentation. At the time several years ago when I rewrote the manual,
using SGML gave me much better HTML, PDF, PS, RTF, and dvi output. As the
DocBook SGML tools are included in most modern Linux releases (RedHat, 7.x,
etc...), they are now an accepted format for free software project
documentation. I commonly come across free software projects with Docbook
format manuals.

> None of the ones that I'm interested in - gcc, binutils, gdb - do.  It 
> is a shame that DejaGnu does as that is the only other tool I really 
> depend on.

  Well, these tools have been around for quite a while, and already have
reasonably complete manuals. Luckily most people rarely ever had anything
to the DejaGnu manual, so I don't think it's a big problem. Adding a few
paragraphs here and there is just a cut and paste job anyway, whether texinfo
or docbook is used.

  At this point though, I have no interest in porting the manual *again* to
switch to texinfo. Too much work, for too little gain.

	- rob -


  reply	other threads:[~2002-04-08 23:48 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 [this message]
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=20020408175713.D21238@welcomehome.org \
    --to=rob@welcomehome.org \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --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