From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NFu7Y-0004E3-5i
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:40:12 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NFu7T-00047b-05
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:40:11 -0500
Received: from [199.232.76.173] (port=38602 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NFu7S-00047K-Qj
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:40:06 -0500
Received: from mail-qy0-f194.google.com ([209.85.221.194]:50003)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NFu7S-0006lu-Hx
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:40:06 -0500
Received: by qyk32 with SMTP id 32so189921qyk.4
	for <qemu-devel@nongnu.org>; Wed, 02 Dec 2009 10:40:06 -0800 (PST)
Message-ID: <4B16B483.6070605@codemonkey.ws>
Date: Wed, 02 Dec 2009 12:40:03 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Unclear committer situation
References: <D2A964B8-EC17-4F48-B778-5A6E1F205E3C@suse.de>
	<fb8d4f70912020733h67de2f02o9946dec71a7108b0@mail.gmail.com>
In-Reply-To: <fb8d4f70912020733h67de2f02o9946dec71a7108b0@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org

Artyom Tarasenko wrote:
> 2009/12/1 Alexander Graf <agraf@suse.de>:
>   
>> 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.
>   

It's still whitespace damaged.  Attaching a second copy as an 
application/octet does not make the situation any better.  Take the time 
to send the patch properly and someone will take the time to 
review/apply it. 

Regards,

Anthony Liguori