From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlgZw-0004Jy-5V for qemu-devel@nongnu.org; Thu, 10 Sep 2009 06:08:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlgZr-0004Fq-VD for qemu-devel@nongnu.org; Thu, 10 Sep 2009 06:08:35 -0400 Received: from [199.232.76.173] (port=47915 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlgZr-0004Fe-KC for qemu-devel@nongnu.org; Thu, 10 Sep 2009 06:08:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:22217) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlgZr-0001sv-1f for qemu-devel@nongnu.org; Thu, 10 Sep 2009 06:08:31 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8AA8TRt004255 for ; Thu, 10 Sep 2009 06:08:29 -0400 Received: from localhost (vpn-9-138.rdu.redhat.com [10.11.9.138]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n8AA8RYK003967 for ; Thu, 10 Sep 2009 06:08:28 -0400 Date: Thu, 10 Sep 2009 15:38:04 +0530 From: Amit Shah Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Message-ID: <20090910100804.GA7992@amit-x200.redhat.com> References: <20090902074905.GB25711@chrom.inf.tu-dresden.de> <20090909121817.GA21997@chrom.inf.tu-dresden.de> <4AA7A6EC.10907@codemonkey.ws> <20090910070336.GD3351@amit-x200.redhat.com> <20090910075644.GA6769@1und1.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20090910075644.GA6769@1und1.de> Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On (Thu) Sep 10 2009 [09:56:44], Reimar D=F6ffinger wrote: > May I repeat my previous question: Is there some CODING file or > something that has some hints? There is: CODIING_STYLE. But that file talks about how to write qemu code. > If not, would a patch to add such a file be welcome? Sure. > I have the impression that some rules for the Linux kernel development > apply, but I wouldn't know out of my head where to find the guide for > that. > (Things that should be in such a file, at least: > - Patches should be sent to this list Yes > - Patches should have [PATCH] in subject Yes > - Patches should be sent as a new thread even when they are in response > to some other mail (not sure about that? I didn't really understand > what that one response I got meant to say, I am just guessing. I also > think it makes quite a mess for people just reading the list and not > trying to apply the patches). Right; that's what seems to be requested. > - Patches are preferred inline, even better created by git format-patch > (not sure about that either) This is right too > - URL of staging tree Might help; but various developers might have their own staging trees (as it now is). If things change in the future, this will have to be modified. > - Possibly coding style rules once decided (no "pointless" casts of voi= d > *)? That should be covered in CODING_STYLE. The list you're talking about makes sense for something like SUBMITTING_PATCHES or CONTRIBUTING. Amit