From: "David S. Miller" <davem@redhat.com>
To: ac131313@cygnus.com
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Sparc/Linux fixes part 1
Date: Sat, 20 Apr 2002 20:18:00 -0000 [thread overview]
Message-ID: <20020420.200957.17345631.davem@redhat.com> (raw)
In-Reply-To: <3CC22CA4.9060300@cygnus.com>
From: Andrew Cagney <ac131313@cygnus.com>
Date: Sat, 20 Apr 2002 23:06:12 -0400
Please also appreciate that GDB runs on international time and most
everyone on this list has a day job. Your changes will be reviewed but
perhaphs not in the timeframe you seem to expect.
My expectation is set based upon how the patches of others
are treated.
I produced a backlog of 12 patches, then Jason Thorpe posted his
patch. You choose to review his change before any of the rest of
mine.
This is not the first time I've seen this kind of thing happen.
And it isn't because foo's patch is simpler than bar's patch, so
don't go down that road.
And honeslty, I find it erroneous to take out on me the fact that the
GDB maintainers don't have the time necessary to do their job. I am
offering my time and assistance, as a mechanism to take some of the
load off of your shoulders.
My objective is to make is so that you need to spend less time on GDB
issues, so that when a Sparc specific bug is fielded, you can push it
to me instead of looking at it yourself.
By complaining that you don't have any time, you create a
self-fulfilling prophecy. Because if you don't review submissions by
"up and coming" people in a timely manner, they get discouraged and go
away instead of eventually becomming "trusted" GDB developers who can
take the load off of your shoulders.
And again, you had time to look at Jason's patch from today and
decided to preempt looking at any of my backlog from the previous
day.
So my offer still stands, either make me sparc maintainer or assure me
that reviews will be performed in a timely manner.
next prev parent reply other threads:[~2002-04-21 3:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 14:54 David S. Miller
2002-04-19 18:37 ` Michael Snyder
2002-04-19 18:43 ` David S. Miller
2002-04-19 18:55 ` David S. Miller
2002-04-19 19:13 ` Andrew Cagney
2002-04-19 19:16 ` David S. Miller
2002-04-19 19:18 ` David S. Miller
2002-04-19 19:46 ` Andrew Cagney
2002-04-19 19:53 ` David S. Miller
2002-04-20 19:01 ` David S. Miller
2002-04-20 19:13 ` Jason R Thorpe
2002-04-20 19:44 ` Andrew Cagney
2002-04-20 20:06 ` Andrew Cagney
2002-04-20 20:18 ` David S. Miller [this message]
2002-04-20 21:24 ` Jason R Thorpe
2002-04-20 21:32 ` David S. Miller
2002-04-20 23:41 ` Andrew Cagney
2002-04-22 9:24 ` Elena Zannoni
2002-04-22 3:55 ` Richard Earnshaw
2002-04-22 4:09 ` David S. Miller
2002-04-19 19:55 ` David S. Miller
2002-04-20 10:00 ` Jason R Thorpe
2002-04-20 17:59 ` David S. Miller
2002-04-20 19:04 ` Jason R Thorpe
2002-04-20 19:19 ` David S. Miller
2002-04-20 19:24 ` Jason R Thorpe
2002-04-20 19:26 ` David S. Miller
2002-04-20 20:32 ` [RFA] Sparc OS abi gdbarch init (was Re: [RFA] Sparc/Linux fixes part 1) David S. Miller
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=20020420.200957.17345631.davem@redhat.com \
--to=davem@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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