From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MnKO3-0000wp-MM
	for qemu-devel@nongnu.org; Mon, 14 Sep 2009 18:51:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MnKNz-0000wI-1e
	for qemu-devel@nongnu.org; Mon, 14 Sep 2009 18:51:07 -0400
Received: from [199.232.76.173] (port=33594 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MnKNy-0000w8-Qi
	for qemu-devel@nongnu.org; Mon, 14 Sep 2009 18:51:02 -0400
Received: from mail-yw0-f203.google.com ([209.85.211.203]:39323)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MnKNy-0002Gn-Ex
	for qemu-devel@nongnu.org; Mon, 14 Sep 2009 18:51:02 -0400
Received: by ywh41 with SMTP id 41so4733882ywh.19
	for <qemu-devel@nongnu.org>; Mon, 14 Sep 2009 15:51:01 -0700 (PDT)
Message-ID: <4AAEC8CC.8030602@codemonkey.ws>
Date: Mon, 14 Sep 2009 17:50:52 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] patchwork service.
References: <200909142331.49181.jcd@tribudubois.net>
In-Reply-To: <200909142331.49181.jcd@tribudubois.net>
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: Jean-Christophe Dubois <jcd@tribudubois.net>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>

Jean-Christophe Dubois wrote:
> I know there is some discussion on how to get earlier feeback to people 
> submitting patches.
>
> It seems there already is a "patchwork" service available.
>
> http://patchwork.ozlabs.org/project/qemu-devel/list/
>
> But it is not used as the patch status is not updated for quite a few of them 
> (even if they have been accepted/merged since then).
>   

I looked at the patchwork tooling and it didn't seem to easily integrate 
into my work flow.  It seems to be designed with the idea that you use 
their tools to pull and manage patches.  I don't think those tools will 
scale to the volume of patches qemu-devel sees though.  Plus, there's no 
easy way to deal with the fact that other maintainers may not use it.  
Now there are a few thousand patches and trolling through would take ages.

Not really sure how to best proceed.  I'm open to suggestions.

Regards,

Anthony Liguori
>
>
>
>