From: Michael Snyder <msnyder@vmware.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: "msnyder@sonic.net" <msnyder@sonic.net>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [commit] replace long output strings
Date: Fri, 07 Jan 2011 23:42:00 -0000 [thread overview]
Message-ID: <4D27A4F3.4000406@vmware.com> (raw)
In-Reply-To: <201101072330.p07NUbRY017926@glazunov.sibelius.xs4all.nl>
Mark Kettenis wrote:
>> Date: Fri, 7 Jan 2011 09:33:51 -0800
>> From: msnyder@sonic.net
>>
>> Restore some long error/warning messages per conversation with Joel.
>
> I agree with Joel that this makes more sense.
Me too. Please feel free to point out others that I should revert
(or just revert them yourselves).
prev parent reply other threads:[~2011-01-07 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 17:34 msnyder
2011-01-07 23:30 ` Mark Kettenis
2011-01-07 23:42 ` Michael Snyder [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=4D27A4F3.4000406@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=msnyder@sonic.net \
/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