From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Napsc-0006SM-HI
	for qemu-devel@nongnu.org; Fri, 29 Jan 2010 07:23:18 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NapsX-0006Qn-Ac
	for qemu-devel@nongnu.org; Fri, 29 Jan 2010 07:23:17 -0500
Received: from [199.232.76.173] (port=43357 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NapsX-0006Qk-5A
	for qemu-devel@nongnu.org; Fri, 29 Jan 2010 07:23:13 -0500
Received: from mx1.redhat.com ([209.132.183.28]:12537)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1NapsV-00077Q-UZ
	for qemu-devel@nongnu.org; Fri, 29 Jan 2010 07:23:12 -0500
Date: Fri, 29 Jan 2010 10:22:02 -0200
From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Merge qemu android
Message-ID: <20100129102202.7e5117d6@doriath>
In-Reply-To: <60cad3f1001281835o1da4f17bjba67fc500411b15b@mail.gmail.com>
References: <195c7a901001210827i29b91f30p3a80c2a8a0c2b4bb@mail.gmail.com>
	<4B5B7AFB.9040506@codemonkey.ws>
	<60cad3f1001281835o1da4f17bjba67fc500411b15b@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
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: David Turner <digit@google.com>
Cc: Bastien ROUCARIES <roucaries.bastien@gmail.com>, qemu-devel@nongnu.org

On Thu, 28 Jan 2010 18:35:16 -0800
David Turner <digit@google.com> wrote:

> Anthony is right, and unfortunately the Android team doesn't have the
> bandwidth to support sending patches to upstream
> at the moment.

 You should also consider the benefits for yourself of merging your bits
upstream: more peer review, more testing, potential improvements and
maybe better integration.

> Note that our version of QEMU is a rather complex mix of 0.8.2 and upstream.
> I routinely cherry pick upstream improvements
> and incorporate them to the codebase. However, I'm also pretty conservative
> and try to avoid stuff we don't depend on and
> which risk breaking other stuff easily so many parts don't get in, or are
> implemented differently.

 Do you ever consider rebasing someday?

> Also, many, many things in the Android emulator codebase have very little
> value for upstream qemu, imho.
> 
> Bastien, what specific features are you interested in ? I can still have a
> look at what would be required to generate the
> corresponding upstream patch.
> 
> On Sat, Jan 23, 2010 at 2:40 PM, Anthony Liguori <anthony@codemonkey.ws>wrote:
> 
> > On 01/21/2010 10:27 AM, Bastien ROUCARIES wrote:
> >
> >> Hi,
> >>
> >> What is the step in order to get qemu android merged mainline ?
> >>
> >> http://android.git.kernel.org/?p=platform/external/qemu.git;a=summary
> >>
> >>
> >
> > Send patches.
> >
> > It's very difficult to merge downstream code unless that entire downstream
> > is committed to working through upstream.  I'd suggest encouraging the
> > Android developers to commit to pushing all of the functionality upstream
> > before going down this path.
> >
> > Regards,
> >
> > Anthony Liguori
> >
> >  Regards
> >>
> >> Bastien
> >>
> >>
> >>
> >>
> >
> >
> >
> >