Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [RFA] Remove Java support
Date: Thu, 06 Oct 2016 16:19:00 -0000	[thread overview]
Message-ID: <877f9lzc0g.fsf@tromey.com> (raw)
In-Reply-To: <635b427e-1e73-be19-482a-c95ef3ed02c0@redhat.com> (Pedro Alves's	message of "Thu, 6 Oct 2016 17:14:49 +0100")

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> Understood.  I was mainly wondering if you thought we should keep it
Pedro> for some reason.  I need to learn to be clearer.

Ok, I understand.  And don't worry about it.
I think it's fine to remove it.

Tom


  reply	other threads:[~2016-10-06 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 14:52 Tom Tromey
2016-10-05 16:04 ` Eli Zaretskii
2016-10-06 13:32 ` Pedro Alves
2016-10-06 15:34   ` Tom Tromey
2016-10-06 16:14     ` Pedro Alves
2016-10-06 16:19       ` Tom Tromey [this message]
2016-10-06 16:40     ` Tom Tromey
2016-10-06 16:45       ` Pedro Alves

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=877f9lzc0g.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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