public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Steven Bosscher" <stevenb.gcc@gmail.com>
To: "Andrew Pinski" <pinskia@physics.uc.edu>,
	 	"GCC Mailing List" <gcc@gcc.gnu.org>,
	richard@codesourcery.com
Subject: Re: Release Schedule issues and doubts
Date: Sun, 04 Jun 2006 09:08:00 -0000	[thread overview]
Message-ID: <571f6b510606040208m31e5e99bm80d0b8751e630ece@mail.gmail.com> (raw)
In-Reply-To: <87lksde4h5.fsf@talisman.home>

On 6/4/06, Richard Sandiford <richard@codesourcery.com> wrote:
> Even if it's not intended that way, your proposal is probably going to
> be interpreted at some stage as a way of punishing maintainers.

And what is wrong with that?  Maybe it would help clean up the long
list of maintainers who don't actually do any maintenance.  Then, at
last, you get a more fair picture of the number of
reviewers&maintainers that we really have. Maybe it turns out that
patches don't get reviewed not because there are not enough
maintainers, but not enough _active_ maintainers.

>  If by
> accepting a patch, you take on the responsibility of organising fixes
> for every problem that gets traced to that patch, there's going to be
> even less incentive to review the thing in the first place.

With power comes responsibility.  If you can't handle the
responsibility, you shouldn't accept the power.  Being a maintainer of
some part of the compiler should be more than just being listed in
MAINTAINERS.

Gr.
Steven

  reply	other threads:[~2006-06-04  9:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03 22:05 Andrew Pinski
2006-06-04  7:59 ` Richard Sandiford
2006-06-04  9:08   ` Steven Bosscher [this message]
2006-06-04 11:52     ` Gerald Pfeifer
2006-06-04 20:19       ` Richard Sandiford
2006-06-04 20:27         ` Andrew Pinski
2006-06-04 20:43           ` Gabriel Dos Reis
2006-06-04 21:08             ` Andrew Pinski
2006-06-04 17:14     ` Mike Stump
2006-06-04 20:03       ` Richard Sandiford
2006-06-04 20:10         ` Andrew Pinski
2006-06-04 20:53           ` Mike Stump
2006-06-04 20:58             ` Andrew Pinski

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=571f6b510606040208m31e5e99bm80d0b8751e630ece@mail.gmail.com \
    --to=stevenb.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pinskia@physics.uc.edu \
    --cc=richard@codesourcery.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).