From: Mark Mitchell <mark@codesourcery.com>
To: Matthias Klose <doko@cs.tu-berlin.de>
Cc: Zack Weinberg <zack@codesourcery.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"debian-gcc@lists.debian.org" <debian-gcc@lists.debian.org>
Subject: Re: [3.2] Reconsider patches for bison 1.50?
Date: Mon, 21 Oct 2002 11:47:00 -0000 [thread overview]
Message-ID: <19190000.1035215137@warlock.codesourcery.com> (raw)
In-Reply-To: <15795.47166.637066.872904@gargle.gargle.HOWL>
--On Monday, October 21, 2002 10:18:06 AM +0200 Matthias Klose
<doko@cs.tu-berlin.de> wrote:
> Mark Mitchell writes:
>> > I think we should reconsider not backporting the patches for bison 1.50
>> > to the 3.2 branch.
>>
>> OK; let's reconsider. Please point me at the patches.
>
> http://gcc.gnu.org/ml/gcc-patches/2002-10/msg00787.html
Very well; go ahead and apply those patches.
Thanks,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
prev parent reply other threads:[~2002-10-21 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 0:56 Zack Weinberg
2002-10-21 2:16 ` Matthias Klose
2002-10-21 8:37 ` Mark Mitchell
2002-10-21 8:40 ` Matthias Klose
2002-10-21 11:47 ` Mark Mitchell [this message]
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=19190000.1035215137@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=debian-gcc@lists.debian.org \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.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).