From: Ken Werner <ken@linux.vnet.ibm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Printing of character vectors
Date: Fri, 02 Jul 2010 14:06:00 -0000 [thread overview]
Message-ID: <201007021605.52853.ken@linux.vnet.ibm.com> (raw)
In-Reply-To: <m363164vv7.fsf@fleche.redhat.com>
On Friday, June 25, 2010 11:59:08 pm you wrote:
> >>>>> "Ken" == Ken Werner <ken@linux.vnet.ibm.com> writes:
> Ken> The attached patch changes c_val_print to additionally check if the
> Ken> type is a vector. Tested on powerpc64-*-linux-gnu and
> Ken> i686-*-linux-gnu, no regressions. Any suggestions are welcome.
>
> The patch itself is fine. I think the only question is what behavior we
> want.
>
> If you don't hear any objections in the next week, go ahead and check it
> in.
>
> Tom
Hi Tom,
A week has passed and it seems there are no objections. As I don't have write
privileges to the repository could you apply the patch please?
Regards
Ken
next prev parent reply other threads:[~2010-07-02 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 8:37 Ken Werner
2010-06-25 21:59 ` Tom Tromey
2010-06-27 17:15 ` Joel Brobecker
2010-07-02 14:06 ` Ken Werner [this message]
2010-07-02 18:03 ` Tom Tromey
2010-07-05 8:18 ` Ken Werner
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=201007021605.52853.ken@linux.vnet.ibm.com \
--to=ken@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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