From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52662 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OnGfx-0005Z3-1y for qemu-devel@nongnu.org; Sun, 22 Aug 2010 16:01:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OnGWO-0005B6-CG for qemu-devel@nongnu.org; Sun, 22 Aug 2010 15:48:01 -0400 Received: from mail-qw0-f45.google.com ([209.85.216.45]:44129) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OnGWO-0005Au-8T for qemu-devel@nongnu.org; Sun, 22 Aug 2010 15:48:00 -0400 Received: by qwh5 with SMTP id 5so4678002qwh.4 for ; Sun, 22 Aug 2010 12:47:59 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4C717A6C.9080805@codemonkey.ws> References: <4C6A4291.1020105@redhat.com> <4C6A8CD8.2080701@codemonkey.ws> <4C71550F.6080602@redhat.com> <4C716F43.8070805@codemonkey.ws> <4C717A6C.9080805@codemonkey.ws> From: Blue Swirl Date: Sun, 22 Aug 2010 19:47:39 +0000 Message-ID: Subject: Re: [Qemu-devel] [PATCH 0/5] CODING_STYLE amendments Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Jes Sorensen , Miguel Di Ciurcio Filho , Markus Armbruster , qemu-devel On Sun, Aug 22, 2010 at 7:28 PM, Anthony Liguori wr= ote: > On 08/22/2010 01:56 PM, Blue Swirl wrote: >>> >>> Why is this even still being discussed? =C2=A0What problem are people a= ctually >>> trying to solve? >>> >>> 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 >> > > That's a hell of a bug :-) Yeah. IIRC I almost dismissed the warning from clang as false positive because I just couldn't see any bug. >>> I don't see a problem with the way things are today. >>> >> >> There is the problem that some patch submitters are reminded of >> CODING_STYLE while others aren't. > > I still think we spend far too much time discussing this on list. =C2=A0W= hile I > stand corrected that we've ever had a bug because of this, I have a hard > time believing this is anywhere in the top 10 list of issues that we have= . When an outsider submits a patch which gets reviewed, CODING_STYLE issues can almost certainly be expected. The other frequent issues (for example memory management) should be addressed by HACKING.