From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Chastain)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/PROBLEMS] document threads/1650, thread internal error
Date: Mon, 26 Jul 2004 17:45:00 -0000 [thread overview]
Message-ID: <9003-Mon26Jul2004204354+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040726154838.4E0E44B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Mon, 26 Jul 2004 11:48:38 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Chastain)
>
> Here is a PROBLEMS entry for gdb/1650, the internal error on
> gdb.threads/manythreads.exp.
Fine with me, thanks.
> Not tested (don't know how to test ascii documentation).
I think posting it here for review is all the ``testing'' it needs.
> Okay to apply to gdb HEAD?
> Okay to apply to gdb gdb_6_2-branch?
Yes, to both, IMHO: documentation can never screw up anything. But
I'll let Andrew to say the definitive YES/NO for the branch part.
next prev parent reply other threads:[~2004-07-26 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 15:48 Michael Chastain
2004-07-26 17:45 ` Eli Zaretskii [this message]
2004-07-27 0:08 ` Michael Chastain
2004-07-26 19:51 ` Andrew Cagney
2004-07-27 0:32 ` Michael Chastain
2004-07-27 15:28 ` Andrew Cagney
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=9003-Mon26Jul2004204354+0300-eliz@gnu.org \
--to=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