From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]*3 Re: [RFC] "info powerpc"
Date: Thu, 15 Sep 2005 19:18:00 -0000 [thread overview]
Message-ID: <200509151917.j8FJHlLX014993@elgar.sibelius.xs4all.nl> (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
>
> On Friday 09 September 2005 16:33, Paul Gilliam wrote:
> > The "Info powerpc" command has no subcommands and does nothing.
> >
> > The testsuit tests "info powerpc altivec"
> >
> > So, should I depreciate 'info powerpc', just get rid of it, or add the 'altivec' subcommand and just point it to 'info vector'?
> >
> > -=# Paul #=-
To be honest, from a multi-platform viewpoint, my favourite would be
to get rid of "info powerpc" completely. But given the fact that we
let the "info powerpc altivec" test slip into the testsuite, and you
seem to like that command, I have no objection to make vector_info()
non-static; your second patch seems too much of a kludge.
Please try to get Andrew's or Kevin's approval though
Mark
next prev parent reply other threads:[~2005-09-15 19:18 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
2005-09-15 19:06 ` [DOC PATCH] " Paul Gilliam
2005-09-16 10:26 ` Eli Zaretskii
2005-09-15 19:18 ` Mark Kettenis [this message]
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=200509151917.j8FJHlLX014993@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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