From: Christopher Faylor <cgf@redhat.com>
To: gcc@gcc.gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: Which version of gdb supports gcc 3.0 ABI?
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <20010314212236.A28674@redhat.com> (raw)
In-Reply-To: <20010314132500.D6148@disaster.jaj.com>
On Wed, Mar 14, 2001 at 01:25:00PM -0500, Phil Edwards wrote:
>I agree with Benjamin here: if they won't approve on a timely basis,
>and won't give you maintainer authority, then fork and do it the Right
>Way.
Daniel is the C++ maintainer for gdb. The problem is that some of the
changes required to fix C++ handling touch on other code like the symbol
table parts of gdb.
I won't go into great details about why there were problems with patch
acceptance but suffice it to say that not all of the problems were due
to the fact that GDB patch approval is (arguably) slow.
So, before anyone draws conclusions on the GDB patch approval process,
please read the gdb and gdb-patches mailing list archives.
>That's great. Well, it's not great that you're frustrated, but that
>you're rewriting it. With years of stuff purged, someday I might be
>able to understand the debugger. :-)
I have Cc'ed the gdb mailing list. If you all have complaints about
gdb, it makes sense to talk about them there.
cgf
next parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103131956.f2DJuCT31263@fillmore.constant.com>
[not found] ` <m2wv9tv0a7.fsf@dynamic-addr-83-177.resnet.rochester.edu>
[not found] ` <20010314132500.D6148@disaster.jaj.com>
2001-03-21 15:59 ` Christopher Faylor [this message]
2001-03-21 15:59 ` Daniel Berlin
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Steinar Bang
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Christopher Faylor
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 Michael Elizabeth Chastain
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=20010314212236.A28674@redhat.com \
--to=cgf@redhat.com \
--cc=gcc@gcc.gnu.org \
--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