From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Status and RFC of patchew testings on QEMU
Date: Thu, 27 Jul 2017 19:03:24 +0800 [thread overview]
Message-ID: <20170727110324.GG5117@lemon.lan> (raw)
In-Reply-To: <CAFEAcA8pH6+aTNznDS7hTDTfNniuSBWgORCaiSm=vkAbukpcLw@mail.gmail.com>
On Tue, 07/25 10:58, Peter Maydell wrote:
> For patchew, I basically ignore patchew compile failure emails
> because it is too painful to get to the bottom of the email
> where the actual error message is because of the pages and
> pages and pages of useless progress output :-(
Isn't it very easy to go to the bottom with a shortcut key and start looking
from there? That's why I thought including the full log in the email isn't a
problem, while not everyone likes web interface when it comes to working on a
long log (I personally find travis web page annoyingly inefficient).
Fam
next prev parent reply other threads:[~2017-07-27 11:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 6:35 [Qemu-devel] Status and RFC of patchew testings on QEMU Fam Zheng
2017-07-17 9:05 ` Stefan Hajnoczi
2017-07-17 9:28 ` Peter Maydell
2017-07-17 9:39 ` Fam Zheng
2017-07-17 10:06 ` Peter Maydell
2017-07-17 10:26 ` Daniel P. Berrange
2017-07-25 9:58 ` Peter Maydell
2017-07-27 11:03 ` Fam Zheng [this message]
2017-07-27 11:30 ` Gerd Hoffmann
2017-07-17 10:03 ` Daniel P. Berrange
2017-07-17 9:41 ` Thomas Huth
2017-07-17 10:20 ` Daniel P. Berrange
2017-07-17 11:00 ` Peter Maydell
2017-07-17 11:06 ` Daniel P. Berrange
2017-07-28 5:59 ` Philippe Mathieu-Daudé
2017-07-17 23:17 ` Fam Zheng
2017-07-18 9:11 ` Thomas Huth
2017-07-18 9:37 ` Peter Maydell
2017-07-18 9:42 ` Daniel P. Berrange
2017-07-19 7:46 ` Fam Zheng
2017-07-17 10:02 ` Daniel P. Berrange
2017-07-21 3:24 ` Fam Zheng
2017-07-17 10:39 ` Kevin Wolf
2017-07-17 10:49 ` Peter Maydell
2017-07-17 11:31 ` Kevin Wolf
2017-07-17 13:40 ` Max Reitz
2017-07-28 5:56 ` Philippe Mathieu-Daudé
2017-07-17 23:28 ` Fam Zheng
2017-07-18 10:14 ` Daniel P. Berrange
2017-07-28 5:46 ` Philippe Mathieu-Daudé
2017-07-28 6:33 ` Fam Zheng
2017-07-28 7:18 ` Cornelia Huck
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=20170727110324.GG5117@lemon.lan \
--to=famz@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).