From: Mark Mitchell <mark@codesourcery.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
"doko@cs.tu-berlin.de" <doko@cs.tu-berlin.de>
Cc: "debian-gcc@lists.debian.org" <debian-gcc@lists.debian.org>,
"gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: gcc-3_2-branch bootstrap failure when using bison-1.50
Date: Tue, 15 Oct 2002 01:34:00 -0000 [thread overview]
Message-ID: <34920000.1034663177@warlock.codesourcery.com> (raw)
In-Reply-To: <200210130308.XAA13661@caip.rutgers.edu>
> I'll leave it to our release manager to decide if this issue warrants
> backporting the relevant patches or not.
I think that your point that we will include the generated files on the
branch is a good one; let's not backport the patches given that.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-10-15 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 5:12 Kaveh R. Ghazi
2002-10-15 1:34 ` Mark Mitchell [this message]
2002-10-15 2:18 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2002-10-13 5:03 Kaveh R. Ghazi
2002-10-13 21:37 ` Matthias Klose
2002-10-14 6:46 ` Akim Demaille
2002-10-14 7:17 ` Akim Demaille
2002-10-15 3:06 ` Matthias Klose
2002-10-12 18:18 Matthias Klose
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=34920000.1034663177@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=debian-gcc@lists.debian.org \
--cc=doko@cs.tu-berlin.de \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
/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).