public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Meador Inge <meadori@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, overseers@sourceware.org
Subject: Re: [PATCH] PR c/53702: Fix -Wunused-local-typedefs with nested functions
Date: Thu, 21 Jun 2012 14:53:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1206211446510.13170@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1340220746-27813-1-git-send-email-meadori@codesourcery.com>

On Wed, 20 Jun 2012, Meador Inge wrote:

> P.S.  If it is OK, then can someone commit for me (I don't have write access)?

This is OK.  You should have write-after-approval access.  Overseers, 
please add user meadori to group gcc.

-- 
Joseph S. Myers
joseph@codesourcery.com

       reply	other threads:[~2012-06-21 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1340220746-27813-1-git-send-email-meadori@codesourcery.com>
2012-06-21 14:53 ` Joseph S. Myers [this message]
2012-06-28 11:01   ` Frank Ch. Eigler

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.1206211446510.13170@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=meadori@codesourcery.com \
    --cc=overseers@sourceware.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).