public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: patch review time
Date: Fri, 04 Mar 2005 22:17:00 -0000	[thread overview]
Message-ID: <20050304221656.GD2419@white> (raw)
In-Reply-To: <01c520e0$Blat.v2.4$f07527a0@zahav.net.il>

On Fri, Mar 04, 2005 at 07:37:10PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 4 Mar 2005 10:54:41 -0500
> > From: Bob Rossi <bob@brasko.net>
> > Cc: gdb@sources.redhat.com
> > 
> > > Please don't start that again.  I told you right there and then that
> > > the i18n changes Andrew was referring to were going slow because of
> > > those who made changes, not because of the review process, since my
> > > comments on the i18n-related patches were posted at most a couple of
> > > days after the RFA, and normally just a few hours after the RFA.
> > 
> > Then let me ask you a qustion. Why did he not bother to get them
> > reviewed? 
> 
> I asked Andrew this question, but didn't get any useful answers.

The only possible solution I could come to, was that he thought patch
review would slow him down to the point were he wouldn't be able to get
work done. Even though you think this isn't the problem, it's the only
conclusion I can draw from his statement. I guess it will be a mystery,
unless of course, he decides to tell us.

> > Well what should I do?
> 
> The only thing to do is to bug the responsible maintainer(s).

What if the particular maintainer is busy? Am I just out of luck? That
doesn't seem very reasonable to me, does it to you?

There must be some other action I can take ...

Thanks,
Bob Rossi

  reply	other threads:[~2005-03-04 22:17 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'
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 [this message]
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=20050304221656.GD2419@white \
    --to=bob@brasko.net \
    --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).