From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Remove output_command_const
Date: Mon, 21 May 2018 20:27:00 -0000 [thread overview]
Message-ID: <87po1og6cr.fsf@tromey.com> (raw)
In-Reply-To: <20180521190539.x7xreiiausan5hud@adacore.com> (Joel Brobecker's message of "Mon, 21 May 2018 15:05:39 -0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> >>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>>
Tom> I happened to notice that output_command_const still exists, but is
Tom> not needed any more -- commands are always const-correct now. This
Tom> patch removes this leftover.
>>
>> Ping.
Joel> Sorry Tom. Looks good to me. I'm trying to think of reasons why
Joel> we wouldn't be allowed to treat this as abvious, and can't think of
Joel> anything... Can anyone else?
Yeah, I probably should've used the obvious rule for this one.
Tom
prev parent reply other threads:[~2018-05-21 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 15:40 Tom Tromey
2018-05-21 16:31 ` Tom Tromey
2018-05-21 19:47 ` Joel Brobecker
2018-05-21 20:27 ` Tom Tromey [this message]
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=87po1og6cr.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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