From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/6.2] Mention threads in NEWS and PROBLEMS
Date: Wed, 28 Jul 2004 14:31:00 -0000 [thread overview]
Message-ID: <4107B8CC.6090001@gnu.org> (raw)
In-Reply-To: <410746E8.nail8HA11UZGF@mindspring.com>
> Looks okay to me, except for the typo: 'occur' rather than 'occure'.
>
> Also I would say '... did not occur with gdb 6.1' rather than
> '... does not occur with gdb 6.1' but I defer to you on whatever
> verb tense you like better.
>
> (As an aside, gdb had only two regressions on i686-pc-linux-gnu when the
> branch was cut, and we've got only one now. This is much better than
> older days when there would be many many more regressions. I hope by
> next release to cover 2-4 native platforms with regression testing.)
Separatly, what about HP/UX? Is that a regression or a long standing bug?
Andrew
next prev parent reply other threads:[~2004-07-28 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 4:08 Andrew Cagney
2004-07-28 6:06 ` Andrew Cagney
2004-07-28 6:25 ` Michael Chastain
2004-07-28 14:31 ` Andrew Cagney [this message]
2004-07-28 21:36 ` Michael Chastain
2004-07-28 18:02 ` Eli Zaretskii
2004-07-28 19:54 ` 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=4107B8CC.6090001@gnu.org \
--to=cagney@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