Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [commit] Mark up add_cmd
Date: Tue, 15 Feb 2005 15:51:00 -0000	[thread overview]
Message-ID: <20050215150722.GA4380@white> (raw)
In-Reply-To: <01c5131a$Blat.v2.4$331ad0c0@zahav.net.il>

On Tue, Feb 15, 2005 at 06:51:47AM +0200, Eli Zaretskii wrote:
> > Date: Mon, 14 Feb 2005 20:57:15 -0500
> > From: Andrew Cagney <cagney@gnu.org>
> > Cc: gdb-patches@sources.redhat.com
> > 
> > It's taken us three months to get through files a-c, simple math tells 
> > us that at that rate we'll finish sometime on '07.  I don't think so.
> 
> I don't know why it took so long, but it certainly isn't because of
> the time it took to review the patch and post the results.  IIRC, none
> of the reviews was ever posted more than a few days after the RFA,
> usually only hours since the RFA was received.
> 
> So this argument cannot possibly justify your decision to bypass the
> normal procedures.

The problem at hand is beyond me, but below is something that does
interest me.

Well, if it is because of long patch review times, this problem needs to
be fixed! Not everyone can just apply patches without getting reviewed.
For instance, my MI patch has been sitting for about 6 weeks on
gdb-patches, and that's not the first patch I've had there. I had a
patch there for 3 months before.

Basically, the GDB patch procedure has been successful at just about
stopping me from doing what I need to do. For some odd reason, I'm very
patient, and am willing to wait months to get what I need done. I don't
think most developers are willing to wait this long. Also, I think it
could honestly be years before I get done what I need to get done. The
procedure needs to change to speed things up!

I remember a while back, when this problem was supposed to be addressed.
What ever happened to the committee that was supposed to address such
problems? I was very hopeful that the committee was going to fix things,
I don't even know if everyone was ever even contacted.

Thanks,
Bob Rossi


  reply	other threads:[~2005-02-15 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 21:45 Andrew Cagney
2005-02-15  2:04 ` Eli Zaretskii
2005-02-15  4:52   ` Andrew Cagney
2005-02-15 15:36     ` Eli Zaretskii
2005-02-15 15:51       ` Bob Rossi [this message]
2005-02-15 17:14         ` Baurzhan Ismagulov
2005-02-15 23:20         ` Eli Zaretskii

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=20050215150722.GA4380@white \
    --to=bob@brasko.net \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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