Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb/PROBLEMS ?
Date: Sun, 02 May 2010 17:05:00 -0000	[thread overview]
Message-ID: <20100502170510.GE2768@adacore.com> (raw)
In-Reply-To: <201005021726.19409.pedro@codesourcery.com>

> I looked over the described problems in gdb/PROBLEMS, and, it looks
> to me that all of them fall in one of two categories: either
> they've been fixed already, or aren't worth mentioning here.

I concur - with a small disclaimer on some of the entries related to
C++, where I do not follow development closely enough.

> I think that if we're not sticking with the policy
> of maintaining the file anymore, we should get rid of the file
> entirely.  If not, we should update the version reference in this file
> as well.  But meanwhile, this is just as good (or better! GDB has
> no problems!), and better than pointing at problems that are gone
> already, for sure.

Now that we have a decent bug tracking system, I think we should, at
most, direct people there. We can keep the PROBLEMS file as a redirect.
Something like this:

---------------------------------------------

                        Known problems in GDB

All known problems in GDB are now documented and tracked through
Bugzilla at: http://sourceware.org/bugzilla/.

---------------------------------------------

But we could also get rid of the file entirely; that would be fine too,
IMO.

-- 
Joel


  reply	other threads:[~2010-05-02 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02 16:26 Pedro Alves
2010-05-02 17:05 ` Joel Brobecker [this message]
2010-05-02 17:38 ` Eli Zaretskii
2010-05-03  1:38 ` Stan Shebs
2010-05-03  3:09   ` Eli Zaretskii
2010-05-03  3:55     ` Stan Shebs
2010-07-29 15:00       ` Pedro Alves

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=20100502170510.GE2768@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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