From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MEQS0-0007hz-9J for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:14:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MEQRv-0007ZM-Is for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:14:55 -0400 Received: from [199.232.76.173] (port=33712 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MEQRv-0007Z7-Ck for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:14:51 -0400 Received: from mx2.redhat.com ([66.187.237.31]:57178) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MEQRv-0005gC-0p for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:14:51 -0400 Date: Wed, 10 Jun 2009 13:20:47 -0300 From: Glauber Costa Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure Message-ID: <20090610162047.GA7776@poweredge.glommer> References: <1244582792-30589-1-git-send-email-ehabkost@redhat.com> <1244582792-30589-3-git-send-email-ehabkost@redhat.com> <87ocsxoye4.fsf@lechat.rtp-net.org> <20090610141255.GZ18045@blackpad> <20090610160742.GB12221@kos.to> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090610160742.GB12221@kos.to> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Riku Voipio Cc: Arnaud Patard , qemu-devel@nongnu.org On Wed, Jun 10, 2009 at 07:07:42PM +0300, Riku Voipio wrote: > On Wed, Jun 10, 2009 at 11:12:55AM -0300, Eduardo Habkost wrote: > > > afaik, they can also be found in maemo's qemu git tree (and sent again > > > later to the mailing list) > > > Why is it not included, if it is a better fix? > > because mainline qemu is lacking a linux-user maintainer. I believe if you can guarantee (through proper testing) the stability of maemo tree, and poke for review the specific parts that may affect the rest ot the world, then it should be fine to just pull it. That's what git allows for, we don't need an "official" maintainer in the commit access sense. Just a trustworthy tree we can pull from.