From: Ben Elliston <bje@au1.ibm.com>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: Andrew Haley <aph@redhat.com>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: increasing the number of GCC reviewers
Date: Wed, 10 Jun 2009 00:45:00 -0000 [thread overview]
Message-ID: <1244594717.11031.29.camel@helios> (raw)
In-Reply-To: <4A2EB45D.1070005@starynkevitch.net>
On Tue, 2009-06-09 at 21:13 +0200, Basile STARYNKEVITCH wrote:
> This is precisely my point. It should be perfectly acceptable that some
> people be authorized to approve some few patches without understanding
> the whole of GCC, and even without knowing all of it.
I sympathise with this point of view, Basile. Over the time I have
worked on GCC, there has been a lot of modularity improvements and
improving the robustness of interfaces throughout the compiler. If this
continues, it should be possible to understand changes in more
isolation. While there will always be consequences that need to be
understood, but that should not apply to every change.
Ben
next prev parent reply other threads:[~2009-06-10 0:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:52 Basile STARYNKEVITCH
2009-06-09 16:45 ` Andrew Haley
2009-06-09 17:17 ` Basile STARYNKEVITCH
2009-06-09 17:20 ` Basile STARYNKEVITCH
2009-06-09 17:31 ` Andrew Haley
2009-06-09 17:55 ` Adam Nemet
2009-06-09 18:01 ` Andrew Haley
2009-06-10 0:14 ` Ben Elliston
2009-06-10 2:05 ` Dave Korn
2009-06-09 19:19 ` Joe Buck
2009-06-09 18:10 ` Paolo Bonzini
2009-06-09 18:10 ` Basile STARYNKEVITCH
2009-06-09 18:21 ` Richard Guenther
2009-06-09 18:42 ` Andrew Haley
2009-06-09 19:13 ` Basile STARYNKEVITCH
2009-06-09 19:29 ` Andrew Haley
2009-06-10 7:45 ` Steven Bosscher
2009-06-10 12:15 ` Richard Kenner
2009-06-10 12:47 ` Joseph S. Myers
2009-06-10 18:12 ` Diego Novillo
2009-06-09 20:22 ` Diego Novillo
2009-06-09 21:10 ` Gabriel Dos Reis
2009-06-09 21:36 ` Tom Tromey
2009-06-10 0:45 ` Ben Elliston [this message]
2009-06-09 21:37 ` Ian Lance Taylor
2009-06-10 0:51 ` Joseph S. Myers
2009-06-10 1:04 ` Ian Lance Taylor
2009-06-10 1:36 ` Tom Tromey
2009-06-10 2:40 ` Daniel Berlin
2009-06-10 11:10 ` Joseph S. Myers
2009-06-10 14:38 ` Paolo Bonzini
2009-06-10 15:00 ` Joseph S. Myers
2009-06-10 14:35 ` Weddington, Eric
2009-06-10 14:52 ` Joseph S. Myers
2009-06-10 15:47 ` Weddington, Eric
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=1244594717.11031.29.camel@helios \
--to=bje@au1.ibm.com \
--cc=aph@redhat.com \
--cc=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
/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).