public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/17255] New: [meta-bug] Fixes that should be back-ported to 3.4 branch
Date: Tue, 31 Aug 2004 22:34:00 -0000	[thread overview]
Message-ID: <20040831223422.17255.mckinlay@redhat.com> (raw)

There are several relatively low-risk bug fixes on gcc HEAD that should be
backported to gcc 3.4. Various upcoming linux distros will ship with gcc 3.4 so
we should get them on to the branch as well.

-- 
           Summary: [meta-bug] Fixes that should be back-ported to 3.4
                    branch
           Product: gcc
           Version: 3.4.2
            Status: UNCONFIRMED
          Keywords: meta-bug
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mckinlay at redhat dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17255


             reply	other threads:[~2004-08-31 22:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 22:34 mckinlay at redhat dot com [this message]
2004-08-31 22:35 ` [Bug java/17255] " mckinlay at redhat dot com
2004-08-31 22:43 ` pinskia at gcc dot gnu dot org
2004-08-31 22:44 ` mckinlay at redhat dot com
2004-09-01 16:00 ` [Bug java/17255] [meta-bug] Fixes " pinskia at gcc dot gnu dot org
2004-09-08 20:34 ` mckinlay at redhat dot com
2004-09-08 20:34 ` mckinlay at redhat dot com
2004-09-09  0:25 ` tromey at gcc dot gnu dot org
2004-11-01  0:46 ` mmitchel at gcc dot gnu dot org
2005-01-25 12:12 ` cvs-commit at gcc dot gnu dot org
2005-05-19 17:31 ` mmitchel at gcc dot gnu dot org
2005-05-19 18:53 ` tromey at gcc dot gnu dot org
2005-05-19 20:31 ` mckinlay at redhat dot com

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=20040831223422.17255.mckinlay@redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).