public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
	Matthias Klose <doko@ubuntu.com>,
	    gcc-patches@sourceware.org, satorux@google.com,
	iant@google.com,     aoliva@redhat.com, dj@redhat.com,
	neroden@gcc.gnu.org,     Ralf.Wildenhues@gmx.de
Subject: Re: [patch] make default linker --hash-style configurable option
Date: Mon, 09 May 2011 17:26:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1105091642500.21102@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4DC81276.8040201@gnu.org>

On Mon, 9 May 2011, Paolo Bonzini wrote:

> On 05/09/2011 05:59 PM, Paul Pluzhnikov wrote:
> > Ping? Ping? Ping? Ping? Ping?
> > 
> > http://gcc.gnu.org/ml/gcc-patches/2011-04/msg00246.html
> > 
> > CC'ing the rest of build system maintainers.
> 
> None of the build system maintainers can approve gcc.c changes.  And those can
> be approved only by either a global reviewer, or by Joseph. That's why I
> haven't replied anything up to now.

I'm thinking of it as a build-system patch with a driver bit - where build 
system maintainers need to decide the general principle of the 
desirability of the feature and what all of the implementation outside 
gcc.c should look like, before it makes sense to review the details of the 
gcc.c bit.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2011-05-09 16:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 18:17 Paul Pluzhnikov
2011-04-04 18:22 ` Rainer Orth
2011-04-04 18:26   ` Ian Lance Taylor
2011-04-04 22:53 ` Matthias Klose
2011-04-05  0:01   ` Joseph S. Myers
2011-04-11 18:01     ` Paul Pluzhnikov
2011-04-18 17:20       ` Paul Pluzhnikov
2011-04-25 17:03         ` Paul Pluzhnikov
2011-05-02 14:23           ` Paul Pluzhnikov
2011-05-02 15:00             ` Joseph S. Myers
2011-05-02 15:57               ` Paul Pluzhnikov
2011-05-09 17:01                 ` Paul Pluzhnikov
2011-05-09 17:04                   ` Paolo Bonzini
2011-05-09 17:26                     ` Joseph S. Myers [this message]
2011-05-09 17:31                       ` Paolo Bonzini
2011-05-09 17:31                         ` Joseph S. Myers
2011-05-09 18:00                           ` Paul Pluzhnikov
2011-05-10 11:36                             ` Richard Guenther
2011-05-10 15:00                               ` Ian Lance Taylor
2011-05-10 15:08                                 ` Jakub Jelinek
2011-05-10 15:23                                 ` Paul Pluzhnikov
2011-05-10 15:26                                   ` Richard Guenther
2011-05-12  9:10 ` Eric Botcazou
2011-05-12  9:19   ` Eric Botcazou
2011-05-12  9:23   ` Paul Pluzhnikov
2011-05-12  9:32     ` Paul Pluzhnikov

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=Pine.LNX.4.64.1105091642500.21102@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=aoliva@redhat.com \
    --cc=bonzini@gnu.org \
    --cc=dj@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@sourceware.org \
    --cc=iant@google.com \
    --cc=neroden@gcc.gnu.org \
    --cc=ppluzhnikov@google.com \
    --cc=satorux@google.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).