All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>,
	Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: QEMU patch queue
Date: Sun, 22 Oct 2006 12:30:48 -0500	[thread overview]
Message-ID: <453BAAC8.5040909@us.ibm.com> (raw)

Howdy,

Are we still maintaining a QEMU patch queue anywhere or are patches just 
going right into unstable?  I took a look at Christian's pq tree on 
xenbits but it appears to have not been updated in a while.

I'm currently looking at the V2E work and there are quite a lot of QEMU 
changes (a lot of which probably get us closer back to mainline).

How do people feel about getting rid of the full QEMU tree in unstable 
and just having a patch queue?  I know there was talk about just using a 
patch queue for linux for 3.0.4.

I'd be willing to submit a patch to add the appropriate makefile magic 
so that make grabbed a copy of QEMU from somewhere and applied the patches.

Regards,

Anthony Liguori

             reply	other threads:[~2006-10-22 17:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22 17:30 Anthony Liguori [this message]
2006-10-22 18:06 ` QEMU patch queue Ian Pratt
2006-10-23  0:37   ` Anthony Liguori

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=453BAAC8.5040909@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 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.