From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: markus.t.metzger@intel.com
Cc: gdb-patches@sourceware.org, markus.t.metzger@gmail.com
Subject: Re: [rfc 1/5] target: add add_deprecated_target_alias
Date: Sun, 10 Feb 2013 22:10:00 -0000 [thread overview]
Message-ID: <20130210221039.GA4819@host2.jankratochvil.net> (raw)
In-Reply-To: <1360337423-27095-2-git-send-email-markus.t.metzger@intel.com>
On Fri, 08 Feb 2013 16:30:19 +0100, markus.t.metzger@intel.com wrote:
> 2013-02-08 Markus Metzger <markus.t.metzger@intel.com>
>
> * target.h (add_deprecated_target_alias): New.
> * target.c (add_deprecated_target_alias): New.
OK for check-in with the nit below.
> --- a/gdb/target.c
> +++ b/gdb/target.c
> @@ -434,6 +434,20 @@ information on the arguments for a particular protocol, type\n\
> add_cmd (t->to_shortname, no_class, t->to_open, t->to_doc, &targetlist);
> }
>
> +/* See target.h. */
> +
> +void
> +add_deprecated_target_alias (struct target_ops *t, char *alias)
> +{
> + struct cmd_list_element *c;
> + char *alt;
> +
> + /* If we use add_alias_cmd, here, we do not get the deprecated warning. */
/* If we use add_alias_cmd, here, we do not get the deprecated warning,
see PR cli/15104. */
> + c = add_cmd (alias, no_class, t->to_open, t->to_doc, &targetlist);
> + alt = xstrprintf ("target %s", t->to_shortname);
> + deprecate_cmd (c, alt);
> +}
> +
> /* Stub functions */
>
> void
Thanks,
Jan
next prev parent reply other threads:[~2013-02-10 22:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 15:30 [rfc 0/5] record-btrace markus.t.metzger
2013-02-08 15:30 ` [rfc 5/5] record, disas: add record disassemble command markus.t.metzger
2013-02-10 22:11 ` Jan Kratochvil
2013-02-08 15:30 ` [rfc 1/5] target: add add_deprecated_target_alias markus.t.metzger
2013-02-10 22:10 ` Jan Kratochvil [this message]
2013-02-08 15:31 ` [rfc 4/5] record: default target methods markus.t.metzger
2013-02-10 22:11 ` Jan Kratochvil
2013-02-08 15:31 ` [rfc 3/5] record: make it build again markus.t.metzger
2013-02-10 22:11 ` Jan Kratochvil
2013-02-11 13:41 ` Metzger, Markus T
2013-02-11 14:15 ` Jan Kratochvil
2013-02-11 17:13 ` [draft patch] <unavailable> unwinder for btrace [Re: [rfc 3/5] record: make it build again] Jan Kratochvil
2013-02-11 21:24 ` Tom Tromey
2013-02-13 7:35 ` Metzger, Markus T
2013-02-13 7:58 ` Jan Kratochvil
2013-02-13 8:08 ` Metzger, Markus T
2013-03-27 18:09 ` Metzger, Markus T
2013-03-28 12:38 ` Markus Metzger
[not found] ` <20130328062747.GA27157@host2.jankratochvil.net>
2013-03-28 14:28 ` Metzger, Markus T
2013-03-28 14:38 ` Jan Kratochvil
2013-03-28 17:37 ` Metzger, Markus T
2013-02-08 15:32 ` [rfc 2/5] record: split record markus.t.metzger
2013-02-10 22:11 ` Jan Kratochvil
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=20130210221039.GA4819@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.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