From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MtHH9-000536-K3 for qemu-devel@nongnu.org; Thu, 01 Oct 2009 04:44:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MtHH4-0004zf-IQ for qemu-devel@nongnu.org; Thu, 01 Oct 2009 04:44:34 -0400 Received: from [199.232.76.173] (port=58890 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MtHH4-0004zX-BL for qemu-devel@nongnu.org; Thu, 01 Oct 2009 04:44:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59724) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtHH3-0004oG-Pq for qemu-devel@nongnu.org; Thu, 01 Oct 2009 04:44:30 -0400 Message-ID: <4AC46BA4.1090503@redhat.com> Date: Thu, 01 Oct 2009 10:43:16 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: CODING_STYLE (was Re: [PATCHv2] qemu: target library, use it in msix) References: <20090923200635.GA21246@redhat.com> <20090924191121.GB29419@redhat.com> <20090929161115.GA13885@redhat.com> <20090930135142.GA20378@redhat.com> <4AC38EA4.70700@redhat.com> <4AC3C70C.4020002@codemonkey.ws> <20091001061721.GC5142@redhat.com> In-Reply-To: <20091001061721.GC5142@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Blue Swirl , Avi Kivity , qemu-devel@nongnu.org Am 01.10.2009 08:17, schrieb Michael S. Tsirkin: > On Wed, Sep 30, 2009 at 04:01:00PM -0500, Anthony Liguori wrote: >> Blue Swirl wrote: >>> On Wed, Sep 30, 2009 at 8:00 PM, Avi Kivity wrote: >>> >>>> On 09/30/2009 03:51 PM, Michael S. Tsirkin wrote: >>>> >>>>> So ... Linux kernel style wins? What do others think? >>>>> >>>>> >>>> Any change is going to cause a large amount of pain if implemented. >>>> >>> >>> True, but with 'indent' support the pain would be brief. >>> >> >> It's equivalent to losing a massive amount of revision history which >> hurts debugging. > > It is? Why is it? git bisect still works. what else do you use > for debugging that gets broken? git blame. Kevin