From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MEQgT-0004v2-HM for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:29:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MEQgR-0004uj-47 for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:29:52 -0400 Received: from [199.232.76.173] (port=34720 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MEQgQ-0004ug-UT for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:29:50 -0400 Received: from lechat.rtp-net.org ([88.191.19.38]:36184) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MEQgQ-00089Z-Gb for qemu-devel@nongnu.org; Wed, 10 Jun 2009 12:29:50 -0400 From: Arnaud Patard (Rtp) Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure 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> <20090610162047.GA7776@poweredge.glommer> Date: Wed, 10 Jun 2009 18:30:49 +0200 In-Reply-To: <20090610162047.GA7776@poweredge.glommer> (Glauber Costa's message of "Wed\, 10 Jun 2009 13\:20\:47 -0300") Message-ID: <874ouonj9i.fsf@lechat.rtp-net.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Glauber Costa Cc: Riku Voipio , qemu-devel@nongnu.org Glauber Costa writes: > 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. At least, this would be better than what we have currently. Please note also that "proper testing" is hard imho. It depends also on host/guest systems used to test. > > 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. Having an "official" maintainer means having someone being able to give his final word if people disagree on how to fix a bug. Arnaud