From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/6] gdbserver (linux_debug): Remove extraneous \n from output.
Date: Wed, 18 Dec 2013 11:14:00 -0000 [thread overview]
Message-ID: <52B18372.7050800@redhat.com> (raw)
In-Reply-To: <yjt28uvjupfe.fsf@ruffy.mtv.corp.google.com>
On 12/17/2013 09:40 PM, Doug Evans wrote:
> Hi.
>
> The blank lines make reading the output hard because one expects them
> to separate major sections not trivial or random ones.
OK, thanks.
> 2013-12-17 Doug Evans <dje@google.com>
>
> * nat/linux-waitpid.c (linux_debug): Remove extraneous \n from output.
(Line too long. fill-column is 74 for ChangeLogs)
--
Pedro Alves
prev parent reply other threads:[~2013-12-18 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 21:40 Doug Evans
2013-12-18 11:14 ` Pedro Alves [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=52B18372.7050800@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).