Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit] Mark up add_cmd
Date: Tue, 15 Feb 2005 23:20:00 -0000	[thread overview]
Message-ID: <01c5139a$Blat.v2.4$3fcfc700@zahav.net.il> (raw)
In-Reply-To: <20050215150722.GA4380@white> (message from Bob Rossi on Tue, 15 Feb 2005 10:07:22 -0500)

> Date: Tue, 15 Feb 2005 10:07:22 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
> 
> > 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!

But I just said (above) that review times for the i18n stuff were a
few days at most, usually less than a day.

> 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.

As far as I'm concerned, the committee doesn't exist.  Witness the
total lack of any reaction from committee members to any of the
arguments we had here lately about the patch review process (or rather
lack thereof).  If the committee doesn't react to such grave problems,
what would it take to get them to move?


      parent reply	other threads:[~2005-02-15 20:10 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
2005-02-15 17:14         ` Baurzhan Ismagulov
2005-02-15 23:20         ` Eli Zaretskii [this message]

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='01c5139a$Blat.v2.4$3fcfc700@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=bob@brasko.net \
    --cc=cagney@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