From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42836) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dagZo-00016C-02 for qemu-devel@nongnu.org; Thu, 27 Jul 2017 07:03:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dagZj-0003NS-UH for qemu-devel@nongnu.org; Thu, 27 Jul 2017 07:03:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36760) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dagZj-0003Mm-PA for qemu-devel@nongnu.org; Thu, 27 Jul 2017 07:03:27 -0400 Date: Thu, 27 Jul 2017 19:03:24 +0800 From: Fam Zheng Message-ID: <20170727110324.GG5117@lemon.lan> References: <20170717063521.GA7393@lemon> <20170717090531.GA7163@stefanha-x1.localdomain> <20170717093944.GA18516@lemon> <20170717102607.GI3640@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] Status and RFC of patchew testings on QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "Daniel P. Berrange" , Stefan Hajnoczi , QEMU Developers 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