qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Status and RFC of patchew testings on QEMU
Date: Mon, 17 Jul 2017 17:39:44 +0800	[thread overview]
Message-ID: <20170717093944.GA18516@lemon> (raw)
In-Reply-To: <CAFEAcA8kt71pbxggfLdP3-WCc8u8v5iijZBksMSq6Yss2ydgiw@mail.gmail.com>

On Mon, 07/17 10:28, Peter Maydell wrote:
> On 17 July 2017 at 10:05, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > On Mon, Jul 17, 2017 at 02:35:21PM +0800, Fam Zheng wrote:
> >> Q1: In the worst case, you get four individual auto replies from patchew. Is
> >> that too many? Do you prefer one reply with all the results concatenated into
> >> one?
> >
> > I'd like to avoid situations where one of the failure emails is sent
> > hours after the others, because it's possible that the patch series
> > author has already sent the next (still broken) revision by that time.
> > The simplest way to avoid that is by sending just one email.
> >
> >> Q2: Some think the full log in the mail body is more than necessary. Is it
> >> better or worse if it is a "tail -n 200" of the log in the body and the full log
> >> attached?
> >
> > tail output and a link to the full logs would be nice.  Often there is a
> > lot of irrelevant output.
> 
> Ideally we'd streamline our make process to not produce so much
> irrelevant output :-)

Does that mean to make "quite-command" absolutely quiet if V=1 is not specified?
;-)

Fam

  reply	other threads:[~2017-07-17  9:39 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 [this message]
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
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=20170717093944.GA18516@lemon \
    --to=famz@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).