From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56799) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2IkW-0000M3-0p for qemu-devel@nongnu.org; Thu, 25 Jul 2013 06:26:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V2IkV-0006tj-5k for qemu-devel@nongnu.org; Thu, 25 Jul 2013 06:26:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:18068) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2IkU-0006te-Se for qemu-devel@nongnu.org; Thu, 25 Jul 2013 06:26:19 -0400 Message-ID: <51F0FD29.9010005@redhat.com> Date: Thu, 25 Jul 2013 12:25:45 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1374501278-31549-1-git-send-email-pbonzini@redhat.com> <87ip02wqvn.fsf@codemonkey.ws> <1374729976.6142.61.camel@pasglop> <1374731256.6142.63.camel@pasglop> <51F0E47D.1060807@redhat.com> <1374742849.6142.72.camel@pasglop> <1374747835.6142.74.camel@pasglop> In-Reply-To: <1374747835.6142.74.camel@pasglop> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/28] Memory API for 1.6: fix I/O port endianness mess List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Herrenschmidt Cc: Peter Maydell , Anthony Liguori , aik@ozlabs.ru, jan.kiszka@siemens.com, qemu-devel@nongnu.org, agraf@suse.de, hpoussin@reactos.org, aurelien@aurel32.net Il 25/07/2013 12:23, Benjamin Herrenschmidt ha scritto: > On Thu, 2013-07-25 at 10:38 +0100, Peter Maydell wrote: >> On 25 July 2013 10:00, Benjamin Herrenschmidt wrote: >>> That's fine, I know you can fix stuff :-) I'm just really annoyed that >>> upstream qemu remained broken for so long (and still is) while the whole >>> thing derailed into a mostly pointless discussion on endianness and >>> nobody (including Alexey) hollered loud enough that the breakage was >>> fairly extensive >> >> I think that for the minor architectures we just have to make >> sure that we do yell loudly when things are broken, because >> the nature of things is that people won't notice. Maybe we should >> have a qemu-urgent list to parallel qemu-trivial for compile >> fixes, reversions of bad breakage, etc, to try to keep them >> out of the general noise ? > > Or I teach Alexey to yell louder (along with some French :-) > > Not sure if a mailing list is useful. A tag might be enough > [REGRESSION] ? [URGENT] ? Those kind of subject tags tend to stand out > pretty well on mailing lists. I've definitely seen them already in the past on qemu-devel, so I concur that a mailing list is not useful. Paolo