From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: 6.0 issues
Date: Mon, 18 Aug 2003 17:16:00 -0000 [thread overview]
Message-ID: <200308181716.h7IHG1IY003490@duracef.shout.net> (raw)
Andrew C says:
- the gdb.cp re-vamp scheduled for near the end of this week
Okay, you and david c both want to do this in the branch, so I will
prepare to do it in the branch. But I might not make it in time. First
I am waiting a few more days for comment, then I do it in HEAD, then I
wait some more time to see if problems come up.
It's fine with me if this misses the release -- I assume it's
okay with you?
> New features shouldn't be going into the 6.0 branch (although there is
> an extreem tollerance towards targets getting their frame code rewritten
> :-).
In this category I would like to add: Mark K's fix for gdb/1338,
"can't backtrace through select".
Michael C
next reply other threads:[~2003-08-18 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 17:16 Michael Elizabeth Chastain [this message]
2003-08-18 17:26 ` Andrew Cagney
2003-08-18 17:44 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 17:52 Michael Elizabeth Chastain
2003-08-18 17:49 ` David Carlton
2003-08-18 15:53 Andrew Cagney
2003-08-18 16:18 ` David Carlton
2003-08-18 16:46 ` Andrew Cagney
2003-08-18 16:56 ` 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=200308181716.h7IHG1IY003490@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).