From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NFtzk-0002De-9X
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:32:08 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NFtzf-00027N-BN
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:32:07 -0500
Received: from [199.232.76.173] (port=60760 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NFtzf-000275-62
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:32:03 -0500
Received: from goliath.siemens.de ([192.35.17.28]:21029)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jan.kiszka@siemens.com>) id 1NFtze-00062I-Ac
	for qemu-devel@nongnu.org; Wed, 02 Dec 2009 13:32:02 -0500
Message-ID: <4B16B29C.40104@siemens.com>
Date: Wed, 02 Dec 2009 19:31:56 +0100
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
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
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: Unclear committer situation
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.
> 

Patch is line-wrapped (following your link to patchwork makes this obvious).

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.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux