From: Bob Rossi <bob@brasko.net>
To: Kip Macy <kmacy@fsmware.com>
Cc: 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 13:45:00 -0000 [thread overview]
Message-ID: <20050306134416.GB5776@white> (raw)
In-Reply-To: <20050305141427.M49469@demos.bsdclusters.com>
On Sat, Mar 05, 2005 at 02:14:55PM -0800, Kip Macy wrote:
> I think Bob may be trying to say that he'd like to be a maintainer ;-)
If this is the only way I can make a significant contribution to GDB
without having a time frame of months to a year, sign me up.
See, I don't care what the mechanism is to allowing an outside
contributor to improve GDB is, I just want find it and do it.
I don't care if Andrew is slow at reviewing my patches, it doesn't make
me mad at Andrew, since everyone has there own time to put towards there
own goals. However, if Andrew as "head maintainer" is not going to change
the GDB development process, to allow any outside contributor (me) to work on
GDB within a reasonable time frame, there then there is a real problem.
I am still trying to figure out if there is a loophole in Andrew's
system (note, I didn't say GDB's system) that will allow an outside contributor
to give back to GDB with in a reasonable amount of time, or if for some reason,
he's trying to block all large amount of contributor's development.
Well, Andrew, is there a loophole?
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.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-03-06 13:45 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 [this message]
2005-03-06 15:57 ` Daniel Jacobowitz
2005-03-06 18:06 ` Bob Rossi
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=20050306134416.GB5776@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).