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


>>> Further to that we need to apply the "proper fix" to  PROBLEMS, NEWS, 
>>> and README, CONTRIBUTE, and TODO. i.e., get them all integrated into the 
>>> doco.
> 
> 
> Sorry, I'm not sure I understand what needs to be done here.

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.

GDB should investigate the same thing.  At present there is a lot of 
redundancy.

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 :-).

Andrew



  reply	other threads:[~2004-03-26 14:17 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 [this message]
2004-03-26 17:53         ` Eli Zaretskii
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=40643B68.8050805@gnu.org \
    --to=cagney@gnu.org \
    --cc=carlton@kealia.com \
    --cc=eliz@gnu.org \
    --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