From: Andrew Haley <aph@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
Andrew Hughes <gnu.andrew@redhat.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: Re: [wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org
Date: Sun, 17 Apr 2016 11:34:00 -0000 [thread overview]
Message-ID: <571374CB.8080604@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1604162229240.9804@anthias.pfeifer.com>
On 16/04/16 21:31, Gerald Pfeifer wrote:
> On Sun, 10 Apr 2016, Andrew Hughes wrote:
>>> That said, looking at the page, and how since 2005 nearly all changes
>>> have been maintainance ones from me, is it really worthwhile keeping
>>> this (short of historic reasons)?
>> I guess the next news will be the removal of GCJ during the
>> GCC 7 development period, so its remaining shelf life should
>> be limited anyway.
>
> Soo, GCC 6 has branched -- would it make sense for you guys to
> start this removal?
Sounds good. OTOH, I don't think there's any great hurry.
> Somewhat related, any concerns if I were to remove
> https://gcc.gnu.org/java/status.html now?
>
> ("Status of GCJ as of GCC 3.2" _really_ is rather old.)
It's so old that I don't think it's of any use. However, I wonder if
it might make more sense to at least have a page saying that GCJ is
gone.
Andrew.
next prev parent reply other threads:[~2016-04-17 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 1:09 Gerald Pfeifer
2016-04-10 21:58 ` Andrew Hughes
2016-04-16 20:32 ` Gerald Pfeifer
2016-04-17 11:34 ` Andrew Haley [this message]
2016-04-17 16:10 ` [wwwdocs,Java] Remove java/status.html Gerald Pfeifer
2016-04-18 9:15 ` Andrew Haley
2016-04-18 22:04 ` [wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org Mike Stump
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=571374CB.8080604@redhat.com \
--to=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=gnu.andrew@redhat.com \
--cc=java-patches@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).