Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: carlton@kealia.com, gdb-patches@sources.redhat.com
Subject: Re: GDB 6.1 "frozen"
Date: Fri, 26 Mar 2004 17:53:00 -0000	[thread overview]
Message-ID: <7137-Fri26Mar2004195020+0300-eliz@gnu.org> (raw)
In-Reply-To: <40643B68.8050805@gnu.org> (message from Andrew Cagney on Fri, 26 Mar 2004 09:17:12 -0500)

> Date: Fri, 26 Mar 2004 09:17:12 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> Long standing todo item:  GCC has a single copy of these and a few other 
> files in the doc/ directory.  The README, INSTALL, ... files are all 
> generated from a single source.

Ah, that one...

Yes, I know about GCC's setup, but I cannot say that I see how it is
so immensely useful to justify any significant effort in doing
something similar in GDB.  IMO, there's nothing wrong with maintaining
a couple of text files.

Also, it is my personal opinion is that text files produced by
makeinfo look awkward, almost ugly, and therefore doing what GCC does
is only justified for large documents that need to be distributed in
Info and other formats as well as in plain text.  Like a FAQ, for
example.

So I'm not going to work on that or encourage others to do it.  But if
someone steps forward and does the job, I won't object to using it if
the results are good and generally useful.

> At present there is a lot of redundancy.

What redundancy is that?

> We should also throw open the question of how to best present release 
> information such as our list of known to work systems, our most serious 
> problems, known bugs, perhaphs even some test results (just, please not 
> today and not for 6.1 :-).

By all means, let's discuss it whenever you are ready.  It's not
urgent, so no need to start that now.


  reply	other threads:[~2004-03-26 17:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 22:48 Andrew Cagney
2004-03-25 23:50 ` David Carlton
2004-03-26  0:14   ` Andrew Cagney
2004-03-26  9:55     ` Eli Zaretskii
2004-03-26 14:17       ` Andrew Cagney
2004-03-26 17:53         ` Eli Zaretskii [this message]
2004-03-26 17:00       ` David Carlton
2004-03-26 17:32         ` Eli Zaretskii
2004-03-26 17:58           ` David Carlton
2004-03-26 18:39             ` Eli Zaretskii

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=7137-Fri26Mar2004195020+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=cagney@gnu.org \
    --cc=carlton@kealia.com \
    --cc=gdb-patches@sources.redhat.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