From: Mike Stump <mrs@apple.com>
To: Ben Elliston <bje@au1.ibm.com>
Cc: Ian Lance Taylor <iant@google.com>, gcc-patches@gcc.gnu.org
Subject: Re: Patch pings
Date: Thu, 18 Jan 2007 02:59:00 -0000 [thread overview]
Message-ID: <B125618F-E6E1-4569-8972-A2669C53D2EA@apple.com> (raw)
In-Reply-To: <1169072479.5748.2.camel@localhost>
On Jan 17, 2007, at 2:21 PM, Ben Elliston wrote:
> At any rate, bother: they don't work with 2.5.4. :-( I don't
> suppose it
> would be possible to raise our minimum version requirement, would it?
The file changes so infrequently and by so few people, that I
actually don't mind bumping the version for flex even though my
system hangs around 2.5.4 currently. I'd propose that we allow the
bump up to 2.5.31. 99% of developers won't even need to update their
flex and no user would need to as we ship the output, right?
Any argument against? (Did you run flex in the past 3 years for
gcc?) If not, maybe someone wouldn't feel bad approving the patch
and doc update... :-)
next prev parent reply other threads:[~2007-01-18 2:59 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
2007-01-17 22:21 ` Ben Elliston
2007-01-18 2:59 ` Mike Stump [this message]
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=B125618F-E6E1-4569-8972-A2669C53D2EA@apple.com \
--to=mrs@apple.com \
--cc=bje@au1.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@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).