Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.kettenis@xs4all.nl, cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit] Add add_setshow_enum_cmd, use in mips
Date: Thu, 11 Nov 2004 05:37:00 -0000	[thread overview]
Message-ID: <20041111053707.GA9394@nevyn.them.org> (raw)
In-Reply-To: <01c4c780$Blat.v2.2.2$bbe98080@zahav.net.il>

On Thu, Nov 11, 2004 at 01:54:16AM +0200, Eli Zaretskii wrote:
> > We can't improve the code quality and design, which have suffered over
> > time, if we can't make progress on patches.  Indeed, the longer it
> > takes for every single change to go in, the less incentive there is to
> > clean anything up!  I'm sure losing incentive to fix things.
> 
> Then let's abandon the patch reviewing procedure completely and just
> commit whatever each one of us global maintainers finds appropriate.
> There are projects that actually work that way (Emacs, for example).
> I have no problem with that, as long as it is consistent and
> documented.

I've suggested something along those lines (not "abandoning patch
reviewing", but giving more authority to the global maintainers)
several times in the past, and met with mixed responses.  I hope to
eventually discuss this question with the GDB Steering Committee, and
get the result documented, one way or another.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-11-11  5:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 17:11 Andrew Cagney
2004-10-30 23:24 ` Eli Zaretskii
2004-10-31 23:01   ` Andrew Cagney
2004-11-01  4:47     ` Eli Zaretskii
2004-11-01  5:12       ` Daniel Jacobowitz
2004-11-01 21:15         ` Eli Zaretskii
2004-11-01 22:37           ` Daniel Jacobowitz
2004-11-02  4:51             ` Eli Zaretskii
2004-11-09  1:15               ` Daniel Jacobowitz
2004-11-09  5:00                 ` Eli Zaretskii
2004-11-09 15:29                   ` Andrew Cagney
2004-11-09 18:42                     ` Daniel Jacobowitz
2004-11-10  4:33                       ` Eli Zaretskii
2004-11-10 20:55                         ` Eli Zaretskii
2004-11-10 21:42                           ` Mark Kettenis
2004-11-10 23:31                             ` Eli Zaretskii
2004-11-10 23:41                               ` Daniel Jacobowitz
2004-11-11  0:00                                 ` Eli Zaretskii
2004-11-11  5:37                                   ` Daniel Jacobowitz [this message]
2004-11-11  5:59                                     ` Joel Brobecker

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=20041111053707.GA9394@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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