From: Eli Zaretskii <eliz@delorie.com>
To: dberlin@redhat.com
Cc: gcc@gcc.gnu.org, 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: <200103150907.EAA27838@indy.delorie.com> (raw)
In-Reply-To: <m2elvzhfgy.fsf@dynamic-addr-83-177.resnet.rochester.edu>
> From: Daniel Berlin <dberlin@redhat.com>
> Date: 14 Mar 2001 22:35:09 -0500
>
> Having some good sense left, i'll just drop out of the discussion
> at this point and get back to work. But there are plently of patches
> that have nothing to do with C++, or even me. It took a month to
> approve Jason Merrill's simple AUTO_MANGLING change (I know it sounds
> like a C++ fix, but it doesn't fall in my maintainership, so it's
> not), for instance. There are plently of examples.
>
> >
> > 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.
> And i'll leave this one alone. Suffice to say there are other problems
> as well, but they are mostly minor compared to patch approval time.
FWIW, I always had the GDB patches I posted as an RFA approved or
commented on in reasonable time (i.e. about a week).
In any case, a fork is not something people should consider easily,
just because someone's patch is not accepted quickly enough.
next prev 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
2001-03-21 15:59 ` Daniel Berlin
2001-03-21 15:59 ` Eli Zaretskii [this message]
2001-03-21 15:59 ` Steinar Bang
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Christopher Faylor
2001-03-21 15:59 ` Eli Zaretskii
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=200103150907.EAA27838@indy.delorie.com \
--to=eliz@delorie.com \
--cc=dberlin@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