From: Tom Tromey <tom@tromey.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
Andrew Burgess <andrew.burgess@embecosm.com>,
gdb-patches@sourceware.org, vapier@gentoo.org
Subject: Re: [PATCH 1/2] sim/opcodes: Allow use of out of tree cgen source directory
Date: Thu, 29 Nov 2018 19:01:00 -0000 [thread overview]
Message-ID: <87y39baet4.fsf@tromey.com> (raw)
In-Reply-To: <5cf23800-dc4b-e85e-8925-28c8648e4d66@FreeBSD.org> (John Baldwin's message of "Tue, 27 Nov 2018 12:03:27 -0800")
>>>>> "John" == John Baldwin <jhb@FreeBSD.org> writes:
John> My vote would actually be to remove it if it isn't really useful. If
John> someone really needs it in the future they can always dig it out of the
John> history.
Me too, especially considering that this is written for a feature that
doesn't exist, and that nobody appears to be working on.
Tom
next prev parent reply other threads:[~2018-11-29 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 17:35 [PATCH 0/2] Allow use of out-of-tree CGEN source Andrew Burgess
2018-11-06 17:35 ` [PATCH 1/2] sim/opcodes: Allow use of out of tree cgen source directory Andrew Burgess
2018-11-26 21:07 ` Simon Marchi
2018-11-27 11:21 ` Andrew Burgess
2018-11-27 19:47 ` Simon Marchi
2018-11-27 20:03 ` John Baldwin
2018-11-29 19:01 ` Tom Tromey [this message]
2018-11-27 20:27 ` Andrew Burgess
2018-11-27 20:31 ` Simon Marchi
2018-11-30 19:07 ` Andrew Burgess
2018-11-30 19:50 ` Tom Tromey
2018-11-06 17:35 ` [PATCH 2/2] sim/cris: Fix references to cgen cpu directory Andrew Burgess
2018-11-30 19:51 ` Tom Tromey
2018-11-26 15:17 ` [PATCH 0/2] Allow use of out-of-tree CGEN source Andrew Burgess
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=87y39baet4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=simon.marchi@polymtl.ca \
--cc=vapier@gentoo.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