From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB respin
Date: Thu, 30 Jan 2003 15:48:00 -0000 [thread overview]
Message-ID: <3E394943.5080902@redhat.com> (raw)
In-Reply-To: <200301300824.h0U8OZL04427@duracef.shout.net>
> [I'm partially back. I can read my mail, and I can run my test bed,
> but I'm not caught up on stuff. -- Michael C]
>
> Andrew Cagney asks:
>
>> Should there be a 5.3.1. So far not much has been comitted to the
>> branch. However, there have been a number of configure / build bug reports.
>
>
> My preference would be to not produce 5.3.1. It seems like a low-yield
> use of resources to me.
>
> Are the configure/build problems fixed in HEAD?
No. Check the bug database for `high' priority `build' problems.
> For those problems which are not fixed in HEAD:
> we need to do that anyways, no matter what
>
> For those problems which are fixed in HEAD:
> ask the bug report submitters to try a HEAD snapshot
> put the PR's into 'FEEDBACK' state
>
> Anyways, I will keep testing and reporting on gdb_5_3-branch.
> My test bed role is separate from my loudmouth role.
:-)
In fact, if the console problem can be resolved, I think there is a very
strong incentive to quickly spin out a 5.4.
Andrew
next prev parent reply other threads:[~2003-01-30 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 8:26 Michael Elizabeth Chastain
2003-01-30 15:48 ` Andrew Cagney [this message]
2003-01-30 17:57 ` Quality Quorum
2003-02-03 12:22 ` Michal Ludvig
-- strict thread matches above, loose matches on Subject: below --
2003-02-03 16:15 Michael Elizabeth Chastain
2003-02-03 17:14 ` Andrew Cagney
2003-02-03 18:08 ` Elena Zannoni
2003-02-03 14:49 Michael Elizabeth Chastain
2003-01-30 16:51 Michael Elizabeth Chastain
2003-01-28 19:46 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=3E394943.5080902@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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