From: 'Bob Rossi' <bob@brasko.net>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, gdb@sources.redhat.com
Subject: Re: patch review time
Date: Fri, 04 Mar 2005 15:36:00 -0000 [thread overview]
Message-ID: <20050304153634.GB2419@white> (raw)
In-Reply-To: <SERRANOjLr2G5vkpNo000000087@SERRANO.CAM.ARTIMI.COM>
On Fri, Mar 04, 2005 at 02:58:45PM -0000, Dave Korn wrote:
> ----Original Message----
> >From: Bob Rossi
> >Sent: 04 March 2005 14:26
>
> > On Fri, Mar 04, 2005 at 09:33:25AM +0200, Eli Zaretskii wrote:
> >>> Date: Thu, 3 Mar 2005 10:00:22 -0500
> >>> From: Bob Rossi
> >>>
> >>> I understand that people are busy, which is the very reason my patches
> >>> take so long to create. However, from my perspective it simply takes to
> >>> long, to get patch reviews done, except of course doco reviews from Eli
> >>> :).
> >>
> >> I think I generally review all patches within my responsibility and/or
> >> area of expertise with the same speed, not only the doco ones.
> >
> > I think you are missing the point here Eli. As an outsider of the GDB
> > project I am complaining that I can't make a significant contribution to
> > GDB because of patch review time.
>
>
> Bob, perhaps it would help if you posted links to any outstanding patches
> for which you are awaiting review?
This isn't about a specific patch, it's about the fact that if it take's
1-2 weeks per patch, there is no way I can get in a large amount of
code. For example, I want to convert the MI testsuite to have the
inferior use a separate pty. I would then like to add a syntax checker
to make sure the output of the MI is correct. After that, I would like
to create Tcl data structures that allow the testsuite to do semantic
analysis on the data. I would like to contribute even more after this ...
The problem is, I could submit 3-4 large patches, but GDB for obvious
reasons won't accept such patches until they are broken down into
multiple small patches. If it takes 1-2 weeks for each of these small
patches, that means realistically, it will take months to possibly a
year to get all of the work I want to get done, done.
If you really must see some patches in waiting,
http://sources.redhat.com/ml/gdb-patches/2005-01/msg00024.html
http://sources.redhat.com/ml/gdb-patches/2005-02/msg00248.html
Also, This isn't about what I have waiting now either, it's about the
fact that I usually wait anywhere from between 1 week (unusual) to
several months.
Bob Rossi
next prev parent reply other threads:[~2005-03-04 15:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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' [this message]
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
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
2005-03-07 4:38 ` Eli Zaretskii
2005-03-07 23:49 ` 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=20050304153634.GB2419@white \
--to=bob@brasko.net \
--cc=dave.korn@artimi.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).