From: Daniel Berlin <dan@cgsoftware.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Daniel Berlin <dan@cgsoftware.com>,
Jim Blandy <jimb@zwingli.cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: Rewriting the type system
Date: Tue, 12 Jun 2001 09:12:00 -0000 [thread overview]
Message-ID: <87k82hisn2.fsf@cgsoftware.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010612114355.1700J-100000@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> On 11 Jun 2001, Daniel Berlin wrote:
>
>> Even the very simple patch to add the misc obstack to the objfiles,
>> and stop putting things in the psymbol obstack that don't belong, from
>> May 29th, hasn't been reviewed yet.
>> Hell, the simple bcache change i submitted last year (updating the
>> starting constant, fix the indenting) still hasn't
>> been reviewed.
>>
>> Jim, GDB development is moving a lot slower than it should.
>
> My experience is very different. Every change that I suggested until
> now, for the past 2 years or so that I'm involved with GDB
> maintenance, was usually reviewed within 1-2 weeks of my posting it
> as an RFA. A few times I needed to post a reminder (I usually do that
> after more than a week's passed without any replies). A couple of
> times, I needed more than one reminder, but that's an exception rather
> than the rule, in my experience.
This is because you work on different parts of GDB then I do.
As I just pointed out to Stan, i'm not alone. I received 4 replies to the
message I posted saying "I know exactly how you feel" or "Your not
kidding". These are people who no longer contribute to GDB, saying
they are waiting for a time when they can get, for instance, a simple
Makefile.in patch, reviewed within 3 months.
That's sad.
>
> In most cases, I had my patches reviewed and approved in 2-3 weeks,
> sometimes a month. In one exceptional case, it took 3 or 4 months,
> but that was my first large submission, and I failed to ping the
> relevant maintainer more than once.
>
> So GDB development is not slow, in my opinion. More importantly, I'm
> always able to get my patches accepted by using the normal channels,
> such as pinging people from time to time.
>
> In other words, the development procedures work.
Maybe for your area of GDB.
Not for mine.
And apparently, not for some others.
Do you really think i'd complain if I was alone here?
If I thought it was just me?
--
"The other day, I was walking my dog around my building... on
the ledge. Some people are afraid of heights. Not me, I'm
afraid of widths.
"-Steven Wright
next prev parent reply other threads:[~2001-06-12 9:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-07 23:22 obvious set_cu_language patch Per Bothner
2001-06-07 23:50 ` Daniel Berlin
2001-06-08 11:01 ` Per Bothner
2001-06-08 14:04 ` Stan Shebs
2001-06-08 14:34 ` Daniel Berlin
2001-06-08 13:04 ` Andrew Cagney
[not found] ` <m2pucevgf6.fsf@kelso.bothner.com>
2001-06-08 13:51 ` Daniel Berlin
[not found] ` <8766e6eke4.fsf@creche.redhat.com>
2001-06-08 14:23 ` Per Bothner
[not found] ` <npelsq28sh.fsf_-_@zwingli.cygnus.com>
2001-06-11 11:43 ` Rewriting the type system Daniel Berlin
2001-06-11 16:58 ` Stan Shebs
2001-06-12 1:44 ` Eli Zaretskii
2001-06-12 9:12 ` Daniel Berlin [this message]
2001-06-12 10:01 ` Eli Zaretskii
2001-06-12 10:16 ` Jim Blandy
2001-06-12 10:44 ` Daniel Berlin
2001-06-12 14:02 ` Stan Shebs
2001-06-13 1:45 ` Eli Zaretskii
2001-06-12 11:08 ` Daniel Berlin
2001-06-12 14:03 ` Andrew Cagney
2001-06-12 21:37 ` Daniel Berlin
2001-06-25 14:13 ` obvious set_cu_language patch Elena Zannoni
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=87k82hisn2.fsf@cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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