From: Daniel Jacobowitz <drow@false.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: [rfa/doco] PROBLEMS: remove pr gdb/1505
Date: Sat, 07 Aug 2004 05:13:00 -0000 [thread overview]
Message-ID: <20040807051342.GA15773@nevyn.them.org> (raw)
In-Reply-To: <41145FDE.nail9GZ1WMY09@mindspring.com>
On Sat, Aug 07, 2004 at 12:51:42AM -0400, Michael Chastain wrote:
> One of the PR's in PROBLEMS has been fixed in gdb HEAD.
> This patch removes the PR from PROBLEMS.
>
> I'm not sure what to put in the title.
> Leaving it as "Known problems in GDB 6.2" is wrong.
> So I changed it "Known problems in GDB HEAD".
>
> Testing: not tested.
>
> Okay to commit?
I'm curious - why do you believe that PR 1505 has been fixed?
Some particular instance may have been, but the problem definitely
remains - see discussion on gdb@ this week.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-08-07 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 4:51 Michael Chastain
2004-08-07 5:13 ` Daniel Jacobowitz [this message]
2004-08-07 7:26 ` Michael Chastain
2004-08-07 16:24 ` Daniel Jacobowitz
2004-08-07 17:04 ` Eli Zaretskii
2004-08-07 22:44 ` Michael Chastain
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=20040807051342.GA15773@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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