qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "Chris Wright" <chrisw@redhat.com>,
	"Stefan Hajnoczi" <stefanha@linux.vnet.ibm.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	"Corey Bryant" <coreyb@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Andreas Färber" <andreas.faerber@web.de>,
	"Avi Kivity" <avi@redhat.com>
Subject: Re: [Qemu-devel] [RFC] QEMU Code Audit Team
Date: Sat, 7 Jan 2012 03:09:27 +0000	[thread overview]
Message-ID: <CAFEAcA_n_QnwK_3_0Qaf7e3f6anYpkafT20ctLgnCRQsZOd+mA@mail.gmail.com> (raw)
In-Reply-To: <4F075CC2.6010700@us.ibm.com>

On 6 January 2012 20:42, Anthony Liguori <aliguori@us.ibm.com> wrote:
> On 01/06/2012 02:02 PM, Andreas Färber wrote:
>> i) Unless it's a build fix, I propose defining a minimum review time
>> before a patch is applied to a (sub)maintainer's queue.

> I disagree here.  If anything, I think we wait a bit too long for people to
> review things and that prevents progress.

Actually I think it would be useful to agree on a "standard" time
for this kind of thing. A lot of the ARM related patches I do don't
get review, and it would be nice to know how long it's sensible to wait
until I can submit them in a pull request. (I don't want to cut
short time for people to review, but I don't want them languishing
on the list for weeks either...)

>> Or should a PULL generally be re-reviewed within a
>> fixed timeframe, questionmark?

We shouldn't be rereviewing pull requests -- they should be basically
equivalent to actual tree commit.

>> It would be nice to have a more explicit process of who pulls from whom
>> and how this is handled during maintainers' absences - especially when
>> approaching a release.

Agreed. In particular it would be nice to have a definite nominated
person who I ought to send target-arm pullreqs to, since all I know
for sure is that it's not Anthony :-)

-- PMM

  reply	other threads:[~2012-01-07  3:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 15:19 [Qemu-devel] [RFC] QEMU Code Audit Team Anthony Liguori
2012-01-06 16:01 ` Stefan Hajnoczi
2012-01-06 16:14   ` Stefan Weil
2012-01-06 16:08 ` Corey Bryant
2012-01-06 17:25   ` Chris Wright
2012-01-08 14:01     ` Dor Laor
2012-01-08 16:54       ` Stefan Hajnoczi
2012-01-06 17:37 ` Chris Wright
2012-01-06 20:02 ` Andreas Färber
2012-01-06 20:42   ` Anthony Liguori
2012-01-07  3:09     ` Peter Maydell [this message]
2012-01-07 10:42       ` Stefan Hajnoczi
2012-01-10 12:58         ` Kevin Wolf
2012-01-10 13:22           ` Anthony Liguori
2012-01-10 13:33             ` Kevin Wolf
2012-01-10 13:39               ` Andreas Färber
2012-01-10 14:55                 ` Kevin Wolf
2012-01-10 15:41                 ` Peter Maydell
2012-01-10 16:31                   ` Andreas Färber
2012-01-10 14:21               ` Anthony Liguori
2012-01-10  3:31 ` Zhi Yong Wu

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=CAFEAcA_n_QnwK_3_0Qaf7e3f6anYpkafT20ctLgnCRQsZOd+mA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=aliguori@us.ibm.com \
    --cc=andreas.faerber@web.de \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=sw@weilnetz.de \
    /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).