From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rjshaw@netspace.net.au, gdb@sources.redhat.com
Subject: Re: patch review time
Date: Sun, 06 Mar 2005 20:29:00 -0000 [thread overview]
Message-ID: <20050306202926.GF5776@white> (raw)
In-Reply-To: <01c5227d$Blat.v2.4$27e1e820@zahav.net.il>
On Sun, Mar 06, 2005 at 08:47:55PM +0200, Eli Zaretskii wrote:
> > Date: Sun, 6 Mar 2005 08:48:04 -0500
> > From: Bob Rossi <bob@brasko.net>
> > Cc: gdb@sources.redhat.com
> >
> > and for some reason, no one else in this community bothers to stand up
> > for what should be right.
>
> I think this is a gross misrepresentation of the reality, to say the
> least. You can find lots of evidence to the contrary in the archives.
>
> Bob, in your justified struggle to get your patches reviewed in a
> timely fashion, please don't start shooting in every direction and
> hurting people who did nothing wrong and have no relation whatsoever
> to your problem.
Eli, I'm sorry if I've done this. You, Daniel Jacobowitz and Michael
Chastain have been *very* helpful to me, as I've been learning and
working with GDB. In fact, Andrew has also been helpful, even if he is
extremely rude about it.
The reason I blame everyone, and not anyone in particular, is because if
the GDB community really cared about contributions from the outside, the
GDB community would change the process to make it happen, no matter what
the cost. I don't know why it is difficult to get patches into GDB/MI in
a timely fashion. I do know that the path needs to open up to allow
this, otherwise GDB, and the community at a whole will suffer.
Since I am no one in the GDB community, I need people that have the
power to give me a solution to get patches into GDB in a timely fashion.
My hope is that I will find that path.
Bob Rossi
next prev parent reply other threads:[~2005-03-06 20:29 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
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 [this message]
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=20050306202926.GF5776@white \
--to=bob@brasko.net \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=rjshaw@netspace.net.au \
/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