From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFuFc-000313-OS for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:48:32 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFuFX-0002tQ-Uj for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:48:32 -0500 Received: from [199.232.76.173] (port=43302 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFuFX-0002tE-Pk for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:48:27 -0500 Received: from mail-gx0-f223.google.com ([209.85.217.223]:42097) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NFuFX-0007SH-Eg for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:48:27 -0500 Received: by gxk23 with SMTP id 23so481012gxk.2 for ; Wed, 02 Dec 2009 10:48:24 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B16B29C.40104@siemens.com> References: <4B16B29C.40104@siemens.com> From: Artyom Tarasenko Date: Wed, 2 Dec 2009 19:48:04 +0100 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Subject: [Qemu-devel] Re: Unclear committer situation List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Blue Swirl , Alexander Graf , qemu-devel@nongnu.org 2009/12/2 Jan Kiszka : > Artyom Tarasenko wrote: >> 2009/12/1 Alexander Graf : >>> Hi, >>> >>> Could someone with commit rights please stand up to feel responsible for >>> 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). Oh. Can it be that a simultaneous inlining and attachment (what Blue Swirl suggested few weeks ago) is not compatible with patchwork? The patch in the attachment doesn't seem to be line-wrapped. Will have to find a way to persuade gmail not to wrap patches. > Note that the merge process can be quite silent. Hearing nothing for a > while (some weeks) may also mean that your patch suddenly pops up in the > tree - given it's clean and no one complained. Already experienced that too. :)