public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Ben Elliston <bje@au1.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Patch pings
Date: Wed, 17 Jan 2007 18:55:00 -0000	[thread overview]
Message-ID: <m3vej5eb6f.fsf@dhcp-172-18-118-195.corp.google.com> (raw)
In-Reply-To: <1169009449.16957.11.camel@localhost>

Ben Elliston <bje@au1.ibm.com> writes:

> The following patches received negligible comment, let alone approval. I
> know they are in some of the less exciting parts of the compiler, so
> perhaps they require a GWP maintainer to approve them?  ;-)
> 
>   PATCH: silence warnings from gengtype-lex.c
>   http://gcc.gnu.org/ml/gcc-patches/2007-01/msg00320.html

gcc/doc/install.texi says that we require flex 2.54 or later.  Ben,
can you confirm that the options you are adding are all supported by
flex 2.54?  If they are, then this patch is approved.

Thanks.

(David Edelsohn suggested on IRC that middle-end maintainers should be
permitted to approve patches to gen* files that generates file which
are part of the middle-end.  If anybody feels that this is
inappropriate, please let me know.)

Ian

  parent reply	other threads:[~2007-01-17 18:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17  4:51 Ben Elliston
2007-01-17 15:00 ` Bernd Schmidt
2007-01-17 18:29 ` Mike Stump
2007-01-17 18:55 ` Ian Lance Taylor [this message]
2007-01-17 22:21   ` Ben Elliston
2007-01-18  2:59     ` Mike Stump
2007-01-18  3:25       ` Ben Elliston
2007-01-19  1:18         ` Ben Elliston
2007-01-17 22:35   ` Ben Elliston
2007-09-23 13:43 Richard Sandiford
2007-09-23 14:30 ` Richard Guenther
2011-04-15 15:15 patch pings Jeff Law
2011-04-15 16:45 ` Bernd Schmidt
2011-04-25 22:41   ` Jeff Law
2014-01-16 17:10 Iyer, Balaji V

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=m3vej5eb6f.fsf@dhcp-172-18-118-195.corp.google.com \
    --to=iant@google.com \
    --cc=bje@au1.ibm.com \
    --cc=gcc-patches@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).