From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S600V-0000LU-3Y for qemu-devel@nongnu.org; Fri, 09 Mar 2012 08:37:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S6006-0006Ko-G1 for qemu-devel@nongnu.org; Fri, 09 Mar 2012 08:37:18 -0500 Received: from mail-pw0-f45.google.com ([209.85.160.45]:50238) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S6006-0006KD-7P for qemu-devel@nongnu.org; Fri, 09 Mar 2012 08:36:54 -0500 Received: by pbcuo5 with SMTP id uo5so2944069pbc.4 for ; Fri, 09 Mar 2012 05:36:52 -0800 (PST) Sender: Paolo Bonzini Message-ID: <4F5A076E.9040904@redhat.com> Date: Fri, 09 Mar 2012 14:36:46 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <4F582EDB.1040608@redhat.com> <4F58B5CB.8040503@codemonkey.ws> <4F58CDEA.2020506@redhat.com> <4F59010C.2060105@codemonkey.ws> <4F5909B3.4080405@redhat.com> <4F590BD7.6030605@codemonkey.ws> <4F5913F3.3040503@redhat.com> <4F591EB4.1090300@codemonkey.ws> In-Reply-To: <4F591EB4.1090300@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] Future goals for autotest and virtualization tests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Lucas Meneghel Rodrigues , Cleber Rosa , QEMU devel , Ademar Reis Il 08/03/2012 22:03, Anthony Liguori ha scritto: >>> >>> >>> Herein lies the problem. You forgot and it's your proposal :-) >> >> Ok, fair enough :) But still, qemu-jeos points out to external >> repositories, >> just as much as buildroot. It seems to me that the whole point about FSF >> requiring the source to be under your control is no longer valid here. > > There aren't qemu-jeos binaries on qemu.org. There won't be until I > mirror the git repos. > > It's the infrastructure that matters here. Submodules provides a nice > infrastructure to handle all of this and minimizing the external > components makes the whole thing much more manageable. How do you handle out-of-tree patches with submodules (as is the case when working on new code)? You want to require tests in order to commit to qemu, but this (for tests where using qtest is not feasible for any reason) requires all drivers to be upstream and accessible to qemu-jeos. Perhaps for this it would make sense to associate a qemu-jeos commit id with an upstream commit (from upstream) + a quilt patch queue. But there's also the problem of embedded devices whose toolchain is not available upstream at all, so you'd need to import those separately and somehow add a different submodule. Paolo