qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Glauber Costa <glommer@redhat.com>
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure
Date: Wed, 10 Jun 2009 18:30:49 +0200	[thread overview]
Message-ID: <874ouonj9i.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <20090610162047.GA7776@poweredge.glommer> (Glauber Costa's message of "Wed\, 10 Jun 2009 13\:20\:47 -0300")

Glauber Costa <glommer@redhat.com> 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

  reply	other threads:[~2009-06-10 16:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 21:26 [Qemu-devel] [PATCH 0/2] linux-user: fix build error against older glibcs Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 1/2] linux-user/syscall.c: define _ATFILE_SOURCE Eduardo Habkost
2009-06-09 21:26 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure Eduardo Habkost
2009-06-09 22:06   ` Arnaud Patard
2009-06-10 14:12     ` Eduardo Habkost
2009-06-10 14:39       ` Arnaud Patard
2009-06-10 19:10         ` Eduardo Habkost
2009-06-10 21:48           ` Riku Voipio
2009-06-10 22:09             ` Eduardo Habkost
2009-06-11 15:14               ` Riku Voipio
2009-06-10 16:07       ` Riku Voipio
2009-06-10 16:20         ` Glauber Costa
2009-06-10 16:30           ` Arnaud Patard [this message]
2009-06-10 16:56             ` Glauber Costa
2009-06-10 22:05               ` Riku Voipio
2009-06-11  8:33                 ` Arnaud Patard
2009-06-11 15:09                   ` Riku Voipio
2009-06-12  8:30                     ` ltp vs linux-user (was: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure) Arnaud Patard
2009-06-11 11:27                 ` [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure vibi sreenivasan
2009-06-12 13:24                 ` vibi sreenivasan
2009-06-10 15:03     ` Glauber Costa
2009-06-10 21:53       ` Riku Voipio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ouonj9i.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=glommer@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).