Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: qiyaoltc@gmail.com, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [RFA 0/3] Fix various bugs found by static analysis
Date: Tue, 04 Oct 2016 19:05:00 -0000	[thread overview]
Message-ID: <8360p8lyui.fsf@gnu.org> (raw)
In-Reply-To: <b6c07add-0604-a9ff-bce3-2828f0044bee@redhat.com> (message from	Pedro Alves on Tue, 4 Oct 2016 19:30:58 +0100)

> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 4 Oct 2016 19:30:58 +0100
> 
> On 10/04/2016 04:14 PM, Yao Qi wrote:
> > On Mon, Oct 3, 2016 at 10:54 PM, Tom Tromey <tom@tromey.com> wrote:
> >>
> >> * PR 20654, incorrect code in java_value_print.  Now that gcj has been
> >>   removed, I think it's probably better to simply remove the Java
> >>   language support.  If this sounds ok, let me know, and I can provide
> >>   a patch.
> >>
> > 
> > I am fine to remove java language support in GDB, but I'd like to hear
> > what other people think about this.
> > 
> 
> I'm fine with removing gcj support, but then again I never really
> needed it personally.

Shouldn't we wait for some time?  I mean, gcj may have been removed,
but that doesn't mean all of its installations have been deleted, or
that no one out there uses the last release, and will use them for
some time.

How about just not making any significant maintenance efforts for it
from now on?


  reply	other threads:[~2016-10-04 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 21:54 Tom Tromey
2016-10-03 21:54 ` [RFA 3/3] PR remote/20655 - small fix in handle_tracepoint_bkpts Tom Tromey
2016-10-04 12:53   ` Yao Qi
2016-10-03 21:54 ` [RFA 1/3] PR symtab/20652 - fix psymbol_compare Tom Tromey
2016-10-04 10:55   ` Yao Qi
2016-10-04 18:37   ` Pedro Alves
2016-10-04 18:52     ` Tom Tromey
2016-10-03 21:54 ` [RFA 2/3] PR gdb/20653 - small cleanup in string_to_explicit_location Tom Tromey
2016-10-03 22:27   ` Keith Seitz
2016-10-04 10:50   ` Yao Qi
2016-10-04 15:14 ` [RFA 0/3] Fix various bugs found by static analysis Yao Qi
2016-10-04 18:31   ` Pedro Alves
2016-10-04 19:05     ` Eli Zaretskii [this message]
2016-10-04 20:43       ` Tom Tromey

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=8360p8lyui.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.com \
    --cc=tom@tromey.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