From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Keir Fraser <keir.xen@gmail.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"Tim.Deegan@citrix.com" <Tim.Deegan@citrix.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: PVH domU patches....
Date: Wed, 31 Jul 2013 14:43:23 -0700 [thread overview]
Message-ID: <20130731144323.297f0fb7@mantra.us.oracle.com> (raw)
Hi,
I noticed the PVH domU patches are still not merged. Just wanna make
sure nothing from me is waited upon. Please let me know. The latest
tree with Tim's acks are at:
git clone git://oss.oracle.com/git/mrathor/xen.git .
git checkout pvh.v10.acked-1
Look forward to seeing them in the unstable tree soon :).
thanks,
Mukesh
next reply other threads:[~2013-07-31 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 21:43 Mukesh Rathor [this message]
2013-08-01 5:50 ` PVH domU patches Keir Fraser
2013-08-01 8:58 ` Andrew Cooper
2013-08-01 18:53 ` Mukesh Rathor
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=20130731144323.297f0fb7@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Tim.Deegan@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir.xen@gmail.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).