From: vibi sreenivasan <vibi_sreenivasan@cms.com>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure
Date: Fri, 12 Jun 2009 18:54:32 +0530 [thread overview]
Message-ID: <1244813072.2099.3.camel@system> (raw)
In-Reply-To: <20090610220540.GE23525@kos.to>
> > > Having an "official" maintainer means having someone being able to give
> > > his final word if people disagree on how to fix a bug.
>
> > One of you should step up and do it.
>
> If nobody objects, I can.
please inform(CC) this to current maintainers & to the authors of file
you are going to maintain.
Thanks & Regards
vibi sreenivasan
>
>
>
>
>
next prev parent reply other threads:[~2009-06-12 13:22 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
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 [this message]
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=1244813072.2099.3.camel@system \
--to=vibi_sreenivasan@cms.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.