From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MleWY-0000xB-QZ for qemu-devel@nongnu.org; Thu, 10 Sep 2009 03:56:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MleWU-0000sr-4B for qemu-devel@nongnu.org; Thu, 10 Sep 2009 03:56:58 -0400 Received: from [199.232.76.173] (port=54409 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MleWT-0000so-Uz for qemu-devel@nongnu.org; Thu, 10 Sep 2009 03:56:53 -0400 Received: from mail.gmx.net ([213.165.64.20]:34312) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MleWT-000518-AZ for qemu-devel@nongnu.org; Thu, 10 Sep 2009 03:56:53 -0400 Date: Thu, 10 Sep 2009 09:56:44 +0200 From: Reimar =?iso-8859-1?Q?D=F6ffinger?= Subject: Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained? Message-ID: <20090910075644.GA6769@1und1.de> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20090910070336.GD3351@amit-x200.redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: qemu-devel@nongnu.org On Thu, Sep 10, 2009 at 12:33:36PM +0530, Amit Shah wrote: > On (Wed) Sep 09 2009 [08:00:28], Anthony Liguori wrote: > > Bernhard Kauer wrote: > >> Its wednesday again, time to resend a patch to the list. > >> Until today the following happened in this endless story: > >> > > > > Really, the whining just makes me want to drop your patch.. > > Let's be courteous and not drive away contributors. > > There's no relation between accepting patches and some nudging on the > contributor's part especially when there's no feedback on patches; > positive or negative. > > If there'd be a daemon sending a mail saying the patch is in some > staging queue it'll reduce everyone's effort. Such extra mails > definitely aren't a problem. If it's later reverted because of any kind > of failure, again a polite mail wouldn't hurt. May I repeat my previous question: Is there some CODING file or something that has some hints? If not, would a patch to add such a file be welcome? 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 - Patches should have [PATCH] in subject - 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). - Patches are preferred inline, even better created by git format-patch (not sure about that either) - URL of staging tree - Possibly coding style rules once decided (no "pointless" casts of void *)? )