From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iclyn-0001FO-8k for qemu-devel@nongnu.org; Tue, 02 Oct 2007 13:56:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iclyh-0001Cu-ND for qemu-devel@nongnu.org; Tue, 02 Oct 2007 13:56:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iclyh-0001Cr-KZ for qemu-devel@nongnu.org; Tue, 02 Oct 2007 13:56:15 -0400 Received: from warsl404pip6.highway.telekom.at ([195.3.96.89] helo=email.aon.at) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Iclyg-0002J2-Ev for qemu-devel@nongnu.org; Tue, 02 Oct 2007 13:56:15 -0400 Date: Tue, 2 Oct 2007 19:56:09 +0200 From: Bernhard Fischer Subject: Re: merge GGI support? [was: Re: [Qemu-devel] [RFC] CRIS target port] Message-ID: <20071002175609.GC13534@aon.at> References: <20071002105745.GB4845@edgar.underground.se.axis.com> <20071002164226.GB13534@aon.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Johannes Schindelin Cc: qemu-devel@nongnu.org, "Edgar E. Iglesias" On Tue, Oct 02, 2007 at 06:32:20PM +0100, Johannes Schindelin wrote: >Hi, >FWIW I would have preferred you following my simple instructions to set up >a fork, but what the heck. ermz, sorry. Thanks :) > >Anybody who fetches the "ggi" branch from my repository on repo.or.cz: >this branch will be rebased. You have been warned. > >> >click on the "fork" link, fill out a small form, and add yourself as user. >> >> Well, ideally i'd like to see the GGI support living directly in the >> upstream repo. If i need to make changes to get it accepted, please let >> me know. > >AFAIR there were license issues with GGI, which made that unfeasible. GGI itself is under the MIT license. IIRC I initially put the qemu-ggi support under BSD. If this is somehow too strict or not appropriate for it being accepted, then i'm very willing to dual license it BSD/GPL if that would help.