From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Andrew Haley <aph@redhat.com>
Cc: Basile STARYNKEVITCH <basile@starynkevitch.net>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: increasing the number of GCC reviewers
Date: Wed, 10 Jun 2009 07:45:00 -0000 [thread overview]
Message-ID: <571f6b510906100045p208c801bo7e1b74ca9039a8cd@mail.gmail.com> (raw)
In-Reply-To: <4A2EB821.8050806@redhat.com>
On Tue, Jun 9, 2009 at 9:29 PM, Andrew Haley<aph@redhat.com> 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.
>
> GCC isn't really like that. Changes in one part can affect things much
> later on, and you really have to know why. That doesn't mean you have
> to understand all of the compiler, but you need to have a lot of
> knowledge.
This is a problem with GCC's lack of modularity, not with Basile's
point of view.
Ciao!
Steven
next prev parent reply other threads:[~2009-06-10 7: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 [this message]
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
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=571f6b510906100045p208c801bo7e1b74ca9039a8cd@mail.gmail.com \
--to=stevenb.gcc@gmail.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).