From: Bob Rossi <bob@brasko.net>
To: Kip Macy <kmacy@fsmware.com>, Nick Roberts <nickrob@snap.net.nz>,
Eli Zaretskii <eliz@gnu.org>,
gdb@sources.redhat.com, cagney@redhat.com, ezannoni@redhat.com,
fnasser@redhat.com
Subject: Re: patch review time
Date: Sun, 06 Mar 2005 18:06:00 -0000 [thread overview]
Message-ID: <20050306180638.GD5776@white> (raw)
In-Reply-To: <20050306155703.GA3332@nevyn.them.org>
On Sun, Mar 06, 2005 at 10:57:04AM -0500, Daniel Jacobowitz wrote:
> On Sun, Mar 06, 2005 at 08:44:16AM -0500, Bob Rossi wrote:
> > Andrew, I'm started to get fed up with your complete lack of response.
> > Will you please take me serious, pick up your role as head maintainer,
> > and respond to my allegations? This way, I'll at least know what the
> > possibilities of accomplishing my goals here are.
>
> Hey, Bob, please take a deep breath and calm down for a little while.
OK.
> Andrew hasn't posted anything to the GDB lists in about a week. That
> suggests that he's either extremely busy, or traveling, or otherwise
> unavailable. Ranting at him for being a human with other obligations
> doesn't get you anywhere, and it doesn't incline anyone else to take
> you seriously.
OK. I can't tell the difference between when he's busy, and when he's
not responding to me. Unfortunately it's all the same.
> I understand your concerns about the system, but you need to consider
> that you're dealing with individuals, not just a system.
Thanks for the advice.
This problem is very serious to me. In fact, I don't have any personal
problems with Andrew, he's reviewed all of my patches and given me good
advice. The problem is, I can't get a serious amount of work done, because
there is no one in the MI area that will review my patches within a reasonable
amount of time. I simply want to fix that problem. Eli told me the only
way to fix the problem was to talk to the head maintainer. Unfortunately for
me, the head maintainer is the only active maintainer for the MI interface.
My question is, what can I do, what options do I have, to contribute a
large amount to the MI interface within a reasonable amount of time?
Everyone involved in GDB should be interested in this question.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-03-06 18:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 20:34 Nick Roberts
2005-03-05 22:06 ` Bob Rossi
2005-03-05 22:15 ` Kip Macy
2005-03-06 13:45 ` Bob Rossi
2005-03-06 15:57 ` Daniel Jacobowitz
2005-03-06 18:06 ` Bob Rossi [this message]
2005-03-06 0:11 ` Russell Shaw
2005-03-06 13:48 ` Bob Rossi
2005-03-06 18:50 ` Eli Zaretskii
2005-03-06 20:17 ` Daniel Berlin
2005-03-06 20:29 ` Bob Rossi
2005-03-07 4:38 ` Eli Zaretskii
2005-03-07 23:49 ` Bob Rossi
-- strict thread matches above, loose matches on Subject: below --
2005-03-03 15:02 Bob Rossi
2005-03-04 7:35 ` Eli Zaretskii
2005-03-04 14:26 ` Bob Rossi
2005-03-04 14:59 ` Dave Korn
2005-03-04 15:36 ` 'Bob Rossi'
2005-03-04 15:43 ` Eli Zaretskii
2005-03-04 15:54 ` Bob Rossi
2005-03-04 17:39 ` Eli Zaretskii
2005-03-04 22:17 ` Bob Rossi
2005-03-05 11:28 ` Eli Zaretskii
2005-03-05 15:27 ` Bob Rossi
2005-03-05 17:13 ` Eli Zaretskii
2005-03-05 17:17 ` Kip Macy
2005-03-06 4:46 ` Eli Zaretskii
2005-03-06 6:24 ` Kip Macy
2005-03-06 18:54 ` Eli Zaretskii
2005-03-06 20:20 ` Bob Rossi
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=20050306180638.GD5776@white \
--to=bob@brasko.net \
--cc=cagney@redhat.com \
--cc=eliz@gnu.org \
--cc=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kmacy@fsmware.com \
--cc=nickrob@snap.net.nz \
/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