From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: muller@ics.u-strasbg.fr (Pierre Muller)
Cc: brobecker@adacore.com ('Joel Brobecker'), gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbadmin/ss/gdb_ari.sh obsolete->regression
Date: Fri, 17 Apr 2009 11:53:00 -0000 [thread overview]
Message-ID: <200904171153.n3HBrWii017152@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <003c01c9bf4e$a95f28f0$fc1d7ad0$@u-strasbg.fr> from "Pierre Muller" at Apr 17, 2009 01:21:31 PM
Pierre Mueller wrote:
> > > In the Legacy category:
> > >
> > > legacy_name (this doesn't exist any more; ARI finds a
> > > local variable with the same name)
>
> I looked at the code in remote.c,
> and I am not sure that this is not what is meant by this rule:
> there is no legacy_name in any ChangeLog, thus it is probably not=20
> a function.
>
> It looks like this legacy argument in add_packet_config_cmd
> add a "set/show remote" entry for
> "binary-download-packet" as an alias of "X-packet".
>
> I am wondering if this reminder is not that we should
> remove that old "binary-download-packet" entry.
> But then there is also still an entry for "binary-download in gdb.texinfo.
Ah, right, the LEGACY category is fully auto-generated anyway;
every identifier named legacy_... will be picked up automatically.
I'm not sure that we even want to get rid of the packet command
aliases; in any case, it's probably not something that needs to
be tracked by ARI, so we might want to change the name of that
local variable.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-04-17 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 21:21 Pierre Muller
2009-04-15 6:38 ` Joel Brobecker
2009-04-15 7:12 ` Pierre Muller
2009-04-15 13:52 ` Ulrich Weigand
2009-04-16 9:35 ` Joel Brobecker
2009-04-17 11:23 ` Pierre Muller
2009-04-17 11:53 ` Ulrich Weigand [this message]
2009-04-16 7:16 ` Joel Brobecker
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=200904171153.n3HBrWii017152@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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