From: Elena Zannoni <ezannoni@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Sparc/Linux fixes part 1
Date: Mon, 22 Apr 2002 09:24:00 -0000 [thread overview]
Message-ID: <15556.14631.337904.379066@localhost.redhat.com> (raw)
In-Reply-To: <20020420.185217.124826922.davem@redhat.com>
David S. Miller writes:
>
> On another topic, I have like 10 or so RFAs pending, and nobody
> provides any feedback. Yet someone else submits a patch after all of
> mine and it gets an RFA quite quickly. It's not like I'm submitting
> jumbo patches or anything, what gives?
>
> I want to maintain and fix up the Sparc port, but I cannot do that
> with multi-day lead times on patch review for even the most simple of
> changes. If nobody has the time to review my changes, then lets vote
> on letting me be the Sparc maintainer because I do have the time to
> keep it in good shape.
>
> If the answer is "we don't have the time, and no you can't become the
> Sparc maintainer", how the heck is someone supposed to become a
> significant contributor to GDB? :(
>
> I want to work on new bugs, failures in the testsuite, but I really
> ought not to do that until my existing work is sorted out.
David, sorry, but I think your expectations are a bit unreasonable.
Michael Snyder, who is the Sparc host maintainer, replied to your
patches up to 7PM Friday night his time (2AM GMT). I assume after that
he had something else to do for the duration of the weekend.
You first complained that your patches had not been reviewed just 4
hours after you submitted them.
While everybody appreciates you fixing the sparc, it is going to take
a bit of time to get your patches reviewed. Please don't think we are
ignoring you. Everybody on this list is doing their best to maintain a
cooperative environment, and so far we have been fairly successful in
this regard.
To facilitate the review process, could I suggest you post a list of
pointers to your pending patches? I have seen a few of them being
checked in, reverted, etc, and it's getting a bit confusing.
Have any of the patches been withdrawn?
Thank you for your understanding.
Elena
next prev parent reply other threads:[~2002-04-22 16:24 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
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 [this message]
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=15556.14631.337904.379066@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=davem@redhat.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