public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/15687] need types_compatible_p
Date: Fri, 04 Jun 2004 20:22:00 -0000 [thread overview]
Message-ID: <20040603224416.719.qmail@sourceware.org> (raw)
In-Reply-To: <20040527173357.15687.tromey@gcc.gnu.org>
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15687
next prev parent reply other threads:[~2004-06-03 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 17:37 [Bug java/15687] New: " tromey at gcc dot gnu dot org
2004-05-27 17:41 ` [Bug java/15687] " pinskia at gcc dot gnu dot org
2004-06-04 20:22 ` pinskia at gcc dot gnu dot org [this message]
2004-09-02 5:15 ` pinskia at gcc dot gnu dot org
[not found] <bug-15687-8172@http.gcc.gnu.org/bugzilla/>
2011-05-22 15:34 ` steven at gcc dot gnu.org
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=20040603224416.719.qmail@sourceware.org \
--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).