public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Jeff Law <law@redhat.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
	 "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	 java-patches@gcc.gnu.org,  Andrew Haley <aph@redhat.com>,
	 Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH, libjava/classpath]: Fix overriding recipe for target 'gjdoc' build warning
Date: Wed, 12 Aug 2015 02:48:00 -0000	[thread overview]
Message-ID: <87mvxxdxys.fsf@tromey.com> (raw)
In-Reply-To: <55CA44C8.7000209@redhat.com> (Jeff Law's message of "Tue, 11 Aug	2015 12:54:00 -0600")

Jeff> It's probably time for the occasional discussion WRT dropping
Jeff> gcj/libjava from the default languages and replace them with either
Jeff> Ada or Go.

It's long past time to remove it.  It's only had minimal maintenance for
years now.  No one is writing new features for it or fixing bugs.  There
aren't any significant users.

I've always felt I should be the one to pull the trigger.  If this is
acceptable I can take a stab at preparing a patch.

I thought maybe this would also enable deleting boehm-gc, zlib, or
libffi; but I see now they all have other users in the tree now.

Tom

  parent reply	other threads:[~2015-08-12  2:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 11:22 Uros Bizjak
2015-08-11 18:03 ` Uros Bizjak
2015-08-11 18:54   ` Jeff Law
2015-08-11 19:24     ` Andrew Haley
2015-08-11 19:34       ` Jeff Law
2015-08-12  2:48     ` Tom Tromey [this message]
2015-08-12 14:44       ` Jeff Law
2015-08-12 14:57         ` Andrew Haley
2015-08-12 16:23           ` Ian Lance Taylor
2015-08-12 16:21         ` Tom Tromey
2015-08-12 16:24           ` Ian Lance Taylor
2015-08-12 16:47             ` Jeff Law
2015-08-12 16:59               ` Ian Lance Taylor
2015-08-13 10:00               ` Richard Biener
2015-08-13 21:31                 ` Jeff Law
2015-08-14  7:44                   ` Richard Biener
2015-08-14  9:24                     ` Andrew Haley
2015-08-20  2:35       ` Andrew Hughes
2015-08-20  4:37         ` Tom Tromey
2015-08-20  8:24           ` Matthias Klose
2015-08-20  8:32             ` Andrew Haley
2015-08-20 14:57               ` Andrew Hughes
2015-08-20 15:27                 ` Andrew Haley
2015-08-20 15:47                   ` Jeff Law
2015-08-20 16:03                     ` Andrew Hughes
2015-08-20 16:08                       ` Andrew Haley
2015-08-20 16:26                         ` Andrew Hughes
2015-08-20 16:38                         ` Richard Biener
2015-08-20 16:39                           ` Andrew Haley
2015-08-20 17:35                       ` Jeff Law
2015-08-20 17:39                         ` Andrew Hughes
2015-08-20 15:52                   ` Andrew Hughes
2015-08-20 16:34                     ` Richard Biener
2015-08-20 16:59                       ` Andrew Hughes
2015-08-20 17:35                         ` Andrew Hughes
2015-08-20 18:05                           ` Richard Biener
2015-08-20 21:06                             ` Joseph Myers
2015-08-20 22:32                             ` Andrew Hughes
2015-08-24 16:39                               ` Jeff Law
2015-08-20 14:58           ` Andrew Hughes
2015-08-20  2:48   ` Andrew Hughes
2015-08-20  6:20     ` Uros Bizjak

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=87mvxxdxys.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=ubizjak@gmail.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).