qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	John Haxby <john.haxby@oracle.com>,
	Alexander Graf <agraf@suse.de>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] How long does it normally take patches to make their way into git?
Date: Wed, 6 Apr 2011 21:23:45 +0100	[thread overview]
Message-ID: <BANLkTimJ+Ci5DgX=6uMAf2=p9CX2dvo19w@mail.gmail.com> (raw)
In-Reply-To: <4D9C7FD7.208@oracle.com>

On Wed, Apr 6, 2011 at 3:59 PM, John Haxby <john.haxby@oracle.com> wrote:
> Hello,
>
> How long does it normally take patches to make their way into git?  I
> only ask because
>
>  [PATCH 1/2][REPOST] Introduce a new 'connected' xendev op called when
> Connected.
>  [PATCH 2/2][REPOST] Move the xenfb pointer handler to the connected method
>
> were (reposted) just under a month ago (11-Mar-2011) and I have a vested
> interest in them :-)
>
> I'm quite happy to wait but I want to make sure that they're acceptable
> and, if so, that they will eventually appear.

This has been discussed recently and there are efforts underway to
improve it, basically we need more active subsystem maintainers to
make the development process scale.

How about Stefano or Anthony Perard collect Xen patches that look good
and have at least one Ack/Reviewed-by and send pull requests to
qemu-devel and "Anthony Liguori" <anthony@codemonkey.ws>?

Stefan

  reply	other threads:[~2011-04-06 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 14:59 [Qemu-devel] How long does it normally take patches to make their way into git? John Haxby
2011-04-06 20:23 ` Stefan Hajnoczi [this message]
2011-04-07 10:11   ` Stefano Stabellini

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='BANLkTimJ+Ci5DgX=6uMAf2=p9CX2dvo19w@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=agraf@suse.de \
    --cc=anthony.perard@citrix.com \
    --cc=john.haxby@oracle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    /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).