From: Michael Chastain <mec.gnu@mindspring.com>
To: eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/PROBLEMS] document threads/1650, thread internal error
Date: Tue, 27 Jul 2004 00:08:00 -0000 [thread overview]
Message-ID: <41059CFD.nailMI61QLUZG@mindspring.com> (raw)
In-Reply-To: <9003-Mon26Jul2004204354+0300-eliz@gnu.org>
eliz> I'll let Andrew to say the definitive YES/NO for the branch part.
Committed to gdb HEAD.
Andrew, how about the branch?
===
2004-07-26 Michael Chastain <mec.gnu@mindspring.com>
Document PR threads/1650.
* PROBLEMS (Threads): Document problem with many threads
next prev parent reply other threads:[~2004-07-27 0:08 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
2004-07-27 0:08 ` Michael Chastain [this message]
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=41059CFD.nailMI61QLUZG@mindspring.com \
--to=mec.gnu@mindspring.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