From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NG8bK-00043r-5d for qemu-devel@nongnu.org; Thu, 03 Dec 2009 05:07:54 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NG8bF-00040N-5P for qemu-devel@nongnu.org; Thu, 03 Dec 2009 05:07:53 -0500 Received: from [199.232.76.173] (port=42893 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NG8bE-000405-5O for qemu-devel@nongnu.org; Thu, 03 Dec 2009 05:07:49 -0500 Received: from mail-gx0-f223.google.com ([209.85.217.223]:49133) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NG8bC-0004fb-Up for qemu-devel@nongnu.org; Thu, 03 Dec 2009 05:07:47 -0500 Received: by gxk23 with SMTP id 23so1168375gxk.2 for ; Thu, 03 Dec 2009 02:07:46 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B16D9BB.5010902@codemonkey.ws> References: <4B16B29C.40104@siemens.com> <4B16D9BB.5010902@codemonkey.ws> From: Artyom Tarasenko Date: Thu, 3 Dec 2009 11:07:26 +0100 Message-ID: Subject: Re: [Qemu-devel] Re: Unclear committer situation Content-Type: text/plain; charset=ISO-8859-1 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: Jan Kiszka , Alexander Graf , qemu-devel@nongnu.org 2009/12/2 Anthony Liguori : > Jan Kiszka wrote: >> >> Artyom Tarasenko wrote: >> >>> >>> 2009/12/1 Alexander Graf : >>> >>>> >>>> Hi, >>>> >>>> Could someone with commit rights please stand up to feel responsible f= or >>>> PPC? >>>> >>>> Usually, when I send a patch to qemu-devel, I know who to address to >>>> increase chances of it getting committed. For kvm/vnc/block I just CC >>>> Anthony, for Audio I just CC malc, etc. >>>> >>> >>> And who can increase chances of getting committed for a scsi-related >>> patch? >>> I sent a patch on November, the 10th >>> (http://patchwork.ozlabs.org/patch/38100/), >>> and it looks like it was just ignored. >>> >>> >> >> Patch is line-wrapped (following your link to patchwork makes this >> obvious). >> >> Note that the merge process can be quite silent. > > Actually, I provided this feedback for the first submission. =A0He resubm= itted > again with the same issue. All you have said was "the patch is whitespace damaged". Does it mean the same as "Attaching everything as "application/octet-stream" is broken"? No. There are multiple possible ways to be whitespace damaged. I assumed the problem had to do with the tabs vs. spaces issue and asked a question how to deal with that. Did anyone answer? No. Blue suggested that you pointed out that one of new lines in the patch was longer than 80 characters. I fixed it and re-submitted. Did anyone say "still broken the same way"? No. I didn't know that there are so many commiters that providing a two sentences response is already a huge overhead for the maintainers. Sorry. Artyom P.S. All my previous patches were also sent through gmail and inlined+attached as "application/octet-stream". Somehow it didn't make problems before.