From: Eli Zaretskii <eliz@gnu.org>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]*3 Re: [RFC] "info powerpc"
Date: Thu, 15 Sep 2005 03:34:00 -0000 [thread overview]
Message-ID: <u64t33syp.fsf@gnu.org> (raw)
In-Reply-To: <200509141710.39794.pgilliam@us.ibm.com> (message from Paul Gilliam on Wed, 14 Sep 2005 17:10:39 -0700)
> From: Paul Gilliam <pgilliam@us.ibm.com>
> Date: Wed, 14 Sep 2005 17:10:39 -0700
>
> The second, 'altivec_alias.patch', functions like the first, except that infcmd.c is not touched. Instead, an 'info powerpc altivec' command
> is added that turns itself into an alias for "info vector" the first time it's called. This can't be done with add_com_alias because the alias and
> the command being aliased are on different command chains.
>
> The final patch, 'no_more_altivec.patch' depreciates the "info powerpc" command prefix and changes the testsuite to use "info vector". To make
> this work, 'lookup_cmd_composition' in cli/cli-decode.c had to be changed so that a prefix command that has no sub-commands
> can be depreciated.
Please accompany any changes to user-visible behavior (such as new
commands or changes in how existing command behave) with appropriate
changes to the user manual. Thanks.
next prev parent reply other threads:[~2005-09-15 3:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 23:32 Paul Gilliam
2005-09-15 0:11 ` [PATCH]*3 " Paul Gilliam
2005-09-15 3:34 ` Eli Zaretskii [this message]
2005-09-15 19:06 ` [DOC PATCH] " Paul Gilliam
2005-09-16 10:26 ` Eli Zaretskii
2005-09-15 19:18 ` Mark Kettenis
2005-09-16 13:56 ` Daniel Jacobowitz
2005-09-16 17:45 ` Kevin Buettner
2005-09-16 18:51 ` Paul Gilliam
2005-09-16 19:40 ` Mark Kettenis
2005-09-16 19:47 ` Kevin Buettner
2005-09-19 17:50 ` [commit] "get rid of info powerpc" Paul Gilliam
2005-09-19 18:09 ` Daniel Jacobowitz
2005-09-20 20:05 ` Paul Gilliam
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=u64t33syp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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