From: Jakub Jelinek <jakub@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: Per Bothner <per@bothner.com>,
Gerald Pfeifer <gerald@pfeifer.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [PATCH] Delete GCJ
Date: Mon, 23 Jan 2017 09:05:00 -0000 [thread overview]
Message-ID: <20170123090503.GH1867@tucnak> (raw)
In-Reply-To: <0b80d6e7-b1f5-e120-7223-76f93f2c6d6d@redhat.com>
On Mon, Jan 23, 2017 at 09:01:24AM +0000, Andrew Haley wrote:
> On 22/01/17 18:41, Per Bothner wrote:
> > In my opinion, all/most of these should be restored.
>
> Because of the historical interest? That's a good point, and perhaps
> I was too hasty. Sorry.
But then it should be probably moved somewhere where Gerald won't have to
spent time maintaining those pages (verification of URLs in there, updating
them when they are moved etc.). Also to make it clear that GCJ is no longer
supported.
Jakub
next prev parent reply other threads:[~2017-01-23 9:05 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 15:13 Andrew Haley
2016-09-05 15:29 ` Matthias Klose
2016-09-05 15:31 ` Andrew Haley
2016-09-05 18:37 ` Eric Gallager
2016-09-05 18:47 ` Andrew Haley
2016-09-05 15:32 ` Matthew Fortune
2016-09-05 15:34 ` Andrew Haley
[not found] ` <FB08E20B-5ED1-45BA-BFA0-11E7807840D2@gmail.com>
2016-09-05 16:17 ` Andrew Haley
2016-09-06 9:06 ` Richard Biener
2016-09-06 9:08 ` Jakub Jelinek
2016-09-06 21:18 ` Jeff Law
2016-09-07 11:41 ` Richard Earnshaw (lists)
2016-09-09 11:03 ` Ian Lance Taylor
2016-09-05 16:26 ` Gerald Pfeifer
2016-09-05 16:30 ` Andrew Haley
2016-09-05 18:40 ` Eric Gallager
2016-09-30 15:34 ` Andrew Haley
2017-01-22 16:51 ` Gerald Pfeifer
2017-01-22 17:17 ` Per Bothner
2017-01-22 18:41 ` Per Bothner
2017-01-23 9:01 ` Andrew Haley
2017-01-23 9:05 ` Jakub Jelinek [this message]
2017-01-23 12:52 ` Per Bothner
2017-01-23 13:42 ` Jakub Jelinek
2017-01-23 14:51 ` Andrew Haley
2017-01-22 18:36 ` Gerald Pfeifer
2016-09-10 12:00 ` NightStrike
2016-09-11 8:25 ` Andrew Haley
2016-09-19 15:26 ` Andrew Hughes
2016-10-03 23:12 ` Matthias Klose
2016-10-04 8:40 ` Rainer Orth
2016-10-04 8:41 ` Andrew Haley
2016-10-04 17:23 ` Mike Stump
2016-10-04 17:25 ` Andrew Pinski
2016-10-04 18:40 ` Iain Sandoe
2016-10-05 16:28 ` Jeff Law
[not found] ` <2b5de569-1efd-f407-49c2-c9fa84cc5315@ubuntu.com>
2016-10-06 16:16 ` Matthias Klose
2016-10-06 16:43 ` Rainer Orth
2016-10-06 16:47 ` Iain Sandoe
2016-10-06 16:54 ` Matthias Klose
2016-10-06 16:56 ` Rainer Orth
2016-10-06 17:10 ` Iain Sandoe
2016-10-06 18:01 ` Mike Stump
2016-10-06 23:59 ` Matthias Klose
2016-10-07 8:31 ` Iain Sandoe
2016-10-10 4:03 ` Matthias Klose
2016-10-10 7:58 ` Iain Sandoe
2016-11-20 20:42 ` Matthias Klose
2016-11-21 5:34 ` Sandra Loosemore
2016-11-21 10:24 ` Iain Sandoe
2016-11-21 12:57 ` Matthias Klose
2016-11-21 16:23 ` Sandra Loosemore
2016-11-21 16:40 ` Matthias Klose
2016-11-21 17:16 ` Peter Bergner
2016-11-21 17:16 ` Rainer Orth
2016-11-21 23:23 ` Matthias Klose
2016-11-22 17:13 ` Sandra Loosemore
2016-11-29 21:23 ` Jeff Law
2016-11-30 1:11 ` Remove stray '@' from install.texi (was Re: [PATCH] Delete GCJ) David Malcolm
2016-11-30 1:20 ` Sandra Loosemore
2016-11-30 1:26 ` David Malcolm
2016-09-05 22:49 [PATCH] Delete GCJ Bernd Edlinger
2016-09-06 0:20 ` Eric Gallager
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=20170123090503.GH1867@tucnak \
--to=jakub@redhat.com \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=java-patches@gcc.gnu.org \
--cc=per@bothner.com \
/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).