From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MysgK-0008Vv-KP
	for qemu-devel@nongnu.org; Fri, 16 Oct 2009 15:41:44 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MysgF-0008T0-Of
	for qemu-devel@nongnu.org; Fri, 16 Oct 2009 15:41:43 -0400
Received: from [199.232.76.173] (port=54442 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MysgF-0008Su-Lo
	for qemu-devel@nongnu.org; Fri, 16 Oct 2009 15:41:39 -0400
Received: from mx1.redhat.com ([209.132.183.28]:41490)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1MysgF-0007u0-5O
	for qemu-devel@nongnu.org; Fri, 16 Oct 2009 15:41:39 -0400
Message-ID: <4AD8CC6D.3050200@redhat.com>
Date: Fri, 16 Oct 2009 21:41:33 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [announce] git patch database
References: <4AD89738.5010904@redhat.com> <4AD8A2DC.2060202@codemonkey.ws>
In-Reply-To: <4AD8A2DC.2060202@codemonkey.ws>
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On 10/16/09 18:44, Anthony Liguori wrote:
> Gerd Hoffmann wrote:
>> Hi folks,
>>
>> I've setup some scripts which extract the patches from the list, sorts
>> them, tries to apply them to master and tries to build them. Results
>> can be checked here:
>>
>> http://repo.or.cz/w/qemu/pdb.git?a=heads
>>
>> Each patch (series) is committed to a new branch. In case something
>> fails the logs are committed, just check out the most recent commit of
>> a failed branch to figure what went wrong.
>
> Basically, a qemu-next type tree. I think this is a really great idea
> and I've been considering suggesting it.
>
> Are you automatically merging branches into a single tree or do you just
> keep each set of patches in their own branch?

Each patch/patchset is in their own branch.  The script also tries to 
merge all patch branches of a day together ($day/merged branch) and 
build it.  Works sometimes, sometimes it doesn't ...

cheers,
   Gerd