From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mypun-0003SL-Cc for qemu-devel@nongnu.org; Fri, 16 Oct 2009 12:44:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mypug-0003L2-Ji for qemu-devel@nongnu.org; Fri, 16 Oct 2009 12:44:28 -0400 Received: from [199.232.76.173] (port=49035 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mypuf-0003Ks-UI for qemu-devel@nongnu.org; Fri, 16 Oct 2009 12:44:22 -0400 Received: from fg-out-1718.google.com ([72.14.220.156]:12093) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mypue-0004X8-P5 for qemu-devel@nongnu.org; Fri, 16 Oct 2009 12:44:21 -0400 Received: by fg-out-1718.google.com with SMTP id 22so344889fge.10 for ; Fri, 16 Oct 2009 09:44:19 -0700 (PDT) Message-ID: <4AD8A2DC.2060202@codemonkey.ws> Date: Fri, 16 Oct 2009 11:44:12 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [announce] git patch database References: <4AD89738.5010904@redhat.com> In-Reply-To: <4AD89738.5010904@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: "qemu-devel@nongnu.org" 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? Regards, Anthony Liguori