From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: QEMU patch queue
Date: Sun, 22 Oct 2006 19:37:15 -0500 [thread overview]
Message-ID: <453C0EBB.3020204@us.ibm.com> (raw)
In-Reply-To: <3AAA99889D105740BE010EB6D5A5A3B2050718@paddington.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> Are we still maintaining a QEMU patch queue anywhere or are patches
>>
> just
>
>> going right into unstable?
>>
>
> There already is a patch queue for QEMU within the unstable tree:
> tools/ioemu/patches/
>
> The full tree is kept as a convenience, but the patch queue is the
> definitive version.
>
There are changesets (such as the recent VNC password) that don't appear
to have corresponding patches in tools/ioemu/patches.
Is the idea to apply the patches to the tree and have the patches in
hg? Should people be submitting patches against tools/ioemu/patches?
Regards,
Anthony Liguori
> Ian
>
prev parent reply other threads:[~2006-10-23 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 17:30 QEMU patch queue Anthony Liguori
2006-10-22 18:06 ` Ian Pratt
2006-10-23 0:37 ` Anthony Liguori [this message]
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=453C0EBB.3020204@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=m+Ian.Pratt@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.