From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=43318 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OnHMZ-0006K2-Gy for qemu-devel@nongnu.org; Sun, 22 Aug 2010 16:41:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OnHMY-00028J-GY for qemu-devel@nongnu.org; Sun, 22 Aug 2010 16:41:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54279) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OnHMY-00028E-AH for qemu-devel@nongnu.org; Sun, 22 Aug 2010 16:41:54 -0400 Message-ID: <4C718B8B.6070406@redhat.com> Date: Sun, 22 Aug 2010 23:41:47 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/5] CODING_STYLE amendments References: <4C6A4291.1020105@redhat.com> <4C6A8CD8.2080701@codemonkey.ws> <4C71550F.6080602@redhat.com> <4C716F43.8070805@codemonkey.ws> <4C71840B.7040409@redhat.com> <4C7185D3.5020506@codemonkey.ws> In-Reply-To: <4C7185D3.5020506@codemonkey.ws> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Blue Swirl , Jes Sorensen , Miguel Di Ciurcio Filho , Markus Armbruster , qemu-devel On 08/22/2010 11:17 PM, Anthony Liguori wrote: > On 08/22/2010 03:09 PM, Avi Kivity wrote: >> On 08/22/2010 09:56 PM, Blue Swirl wrote: >>> >>>> Can someone point to a bug in QEMU that's been caused because of >>>> CODING_STYLE or the fact that some patches don't adhere to it? >>> 7b1df88f284f462ecb236931ad863a815f243195 >> >> How was this bug caused by CODING_STYLE? In fact, if CODING_STYLE >> was applied correctly then this bug would stand out much more: >> >> if (...) { >> /* .... */; >> } >> return; > > "or the fact that some patches don't adhere to it". If CODING_STYLE > was enforced at commit time, this bug would not have happened most > likely. Ah, yes. > > But it's such an odd case that I'd say it's just the exception that > proves the rule that a loose CODING_STYLE isn't significantly > impacting overall quality. I agree. IMO a consistent coding style is mainly an aid to the reader, the brain has one less thing to disentangle. > I also don't believe that it's creating distress in contributors. I > believe timely patch review/commit is probably a more important issue > for contributors than whether some people get by without CODING_STYLE > being strictly enforced. Definitely. Especially as people can adjust to CODING_STYLE. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.