From: "Andrew Burgess" <aburgess@broadcom.com>
To: gdb-patches@sourceware.org
Cc: "Mike Frysinger" <vapier@gentoo.org>
Subject: Re: [PATCH] more output from remote-sim dump_mem
Date: Tue, 02 Oct 2012 21:54:00 -0000 [thread overview]
Message-ID: <506B628A.7020601@broadcom.com> (raw)
In-Reply-To: <201210021720.25317.vapier@gentoo.org>
On 02/10/2012 10:20 PM, Mike Frysinger wrote:
>
> you could hoist the \t printf to the top and \n to the bottom and keep the
> center focused on the 0x output.
>
Committed with the change you suggested.
Thanks for the review.
Andrew
prev parent reply other threads:[~2012-10-02 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 21:07 Andrew Burgess
2012-10-02 21:20 ` Mike Frysinger
2012-10-02 21:54 ` Andrew Burgess [this message]
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=506B628A.7020601@broadcom.com \
--to=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
/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