From: Daniel Berlin <dan@cgsoftware.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Daniel Berlin <dan@cgsoftware.com>, Jim Blandy <jimb@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: Rewriting the type system
Date: Tue, 12 Jun 2001 21:37:00 -0000 [thread overview]
Message-ID: <87bsntf10x.fsf@cgsoftware.com> (raw)
In-Reply-To: <3B2683A7.9020508@cygnus.com>
Andrew Cagney <ac131313@cygnus.com> writes:
>> Hell, the simple bcache change i submitted last year (updating the
>> starting constant, fix the indenting) still hasn't
>> been reviewed.
>
>
> This patch?
Yup.
>
> I'm suprized you didn't take the initiative here and check it in as an
> obvious fix.
Really?
It's in Jim's area.
Jim tells me my patches aren't correct.
Don't you think "taking the initiative" and just up and checking it in would
step on his toes a little bit?
Believe it or not, I tried to avoid doing this when possible, which it
wasn't always in order to get stuff done.
We also had no clear ruling on the obvious fix rule yet, anyway.
Besides, if it's an obvious fix, why didn't he just take a few minutes to
look it over when it arrived in his inbox (you'll note the original
message was copied to him), and reply "looks okay"? Since if it's
obvious, it shouldn't take him more than probably 1 or 2 minutes to
look over a 20-30 line patch.
Just like a software project becomes late one day at a time, GDB is
improved one patch at a time.
If some of you maintainer guys and gals (i'm no longer a maintainer,
so it's not "we") ignore small patches (and i'm not implying any one
particular person does),
A. You won't get the effect a piling up of small improvements has.
B. You won't spur the people who made the small changes to make
larger, more ambitious ones.
I haven't touched the bcache since submitting that patch, and getting
no response. It's not because the bcache is perfect. It's because who
the heck wants to make large changes to anything if they'll just go
off into a void?
>
>
> Andrew
>
--
"I have two very rare photographs. One is a picture of Houdini
locking his keys in his car. The other is a rare photograph of
Norman Rockwell beating up a child.
"-Steven Wright
next prev parent reply other threads:[~2001-06-12 21:37 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
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 [this message]
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=87bsntf10x.fsf@cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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