From: Tom Tromey <tom@tromey.com>
To: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] gdb: introduce new 'maint flush ' prefix command
Date: Thu, 03 Dec 2020 10:23:52 -0700 [thread overview]
Message-ID: <874kl2dcrb.fsf@tromey.com> (raw)
In-Reply-To: <e0e772a6-e7ee-9520-1a48-99e264e648d6@linaro.org> (Luis Machado via Gdb-patches's message of "Mon, 23 Nov 2020 13:24:25 -0300")
Luis> Should we keep testing the alias in some way though? I see the
Luis> testcases have been updated to only use the new command. We should
Luis> certify that the old ones still exist and work?
I'm ok with not adding a test in this case, since it's a deprecated
alias of a maintenance command.
Luis> If we plan to drop the old commands at some point (I think it makes
Luis> sense), we should probably mark them as deprecated with a set removal
Luis> date.
Definitely agreed about deprecation.
We haven't normally set dates before, but it seems like a good idea.
Normally deprecated things just stick around more or less forever.
Tom
next prev parent reply other threads:[~2020-12-03 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 10:39 [PATCH 0/2] Organise maintenance commands that flush caches Andrew Burgess
2020-11-23 10:39 ` [PATCH 1/2] gdb: introduce new 'maint flush ' prefix command Andrew Burgess
2020-11-23 15:28 ` Eli Zaretskii via Gdb-patches
2020-11-23 16:24 ` Luis Machado via Gdb-patches
2020-12-03 17:23 ` Tom Tromey [this message]
2020-12-13 12:43 ` Andrew Burgess
2020-11-23 10:39 ` [PATCH 2/2] gdb: new command 'maint flush dcache' Andrew Burgess
2020-11-23 15:28 ` Eli Zaretskii via Gdb-patches
2020-11-23 16:28 ` Luis Machado via Gdb-patches
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=874kl2dcrb.fsf@tromey.com \
--to=tom@tromey.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