From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52489 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OlHOt-0000jK-0W for qemu-devel@nongnu.org; Tue, 17 Aug 2010 04:20:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OlHOr-0004OW-8S for qemu-devel@nongnu.org; Tue, 17 Aug 2010 04:20:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52569) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OlHOr-0004OJ-1x for qemu-devel@nongnu.org; Tue, 17 Aug 2010 04:20:01 -0400 Message-ID: <4C6A462A.606@redhat.com> Date: Tue, 17 Aug 2010 10:19:54 +0200 From: Jes Sorensen MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: Unmaintained QEMU builds References: <4C62825A.6000903@mail.berlios.de> <4C62E980.9090707@mail.berlios.de> <4C62FBFE.8050801@mail.berlios.de> <4C63204D.4080009@redhat.com> <4C63BC16.8040708@mail.berlios.de> In-Reply-To: <4C63BC16.8040708@mail.berlios.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: Blue Swirl , Paolo Bonzini , QEMU Developers On 08/12/10 11:17, Stefan Weil wrote: > Am 12.08.2010 00:12, schrieb Paolo Bonzini: > Jes has an opinion how thinks should be done, and I have a different one. > If you read the complete history, you can see that I suggested a > compromise (*) > which would give the same result as Jes' suggestions. Only the steps > to reach this result were different, and I have good reasons why I > prefer my way to do them. Both ways require two commits, so > there would be no difference for the community nor for the > committers. > > I did not reply to Jes' last mail because he claims to represent the > community without accepting that others (in this case me) who are > also part of the community might have good reason for their approach, too. > His mail was also very impolite which is one more reason why I > did not reply. I gave you plenty technical reasons for doing things the right way, and you did agree that it should go to the right place. However rather than doing the small job it was to fix up the patch, you decided to ignore it. It's a real shame your patch was applied the way it was. The net result of it is that someone doing a git bisect on the tree will end up with a broken build they have to work around. Frankly if anyone here is impolite, it is you for trying to force in patches that breaks debugging. Jes