From: Andrew Haley <aph@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs,Java] Obsolete GCJ FAQ entry for Solaris?
Date: Fri, 21 Dec 2012 09:51:00 -0000 [thread overview]
Message-ID: <50D43110.7090209@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1212201801500.2358@tuna.site>
On 12/21/2012 04:02 AM, Gerald Pfeifer wrote:
> PING.
>
> On Fri, 2 Nov 2012, Gerald Pfeifer wrote:
>> Rainer (or others),
>>
>> the FAQ entry below seems obsolete to me (dates back more than a
>> decade). Shall we remove it, or is there something else we still
>> should document (in addition to gcc/doc/install.texi)?
OK, thanks.
Andrew.
prev parent reply other threads:[~2012-12-21 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 20:32 Gerald Pfeifer
2012-12-21 4:02 ` Gerald Pfeifer
2012-12-21 9:51 ` Andrew Haley [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=50D43110.7090209@redhat.com \
--to=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=java-patches@gcc.gnu.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).