Over the last week I've been migrating the Xen paravirt_ops tree from a
Mercurial patch-queue based model to a git tree. This makes it easier
for me to work with the various Linux kernel subsystem maintainers in
upstreaming patches, but it should also make it easier for people in the
Xen community to contribute to mainline Xen development.

At the moment the git tree is hosted on kernel.org at
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git

If you want to get started, either xen/dom0/hackery or xen/master are
the places to start;

xen/dom0/hackery
Master dom0 branch. This is all the interesting dom0-related topic
branches merged together, and is a superset of xen/master.
xen/master
Master domU branch, with everything interesting merged in. This is
likely to be more stable and closer to upstream than dom0/hackery.

If you want to do development against this tree, branch off the most
appropriate topic branch and get hacking, and tell me when you have
something you want me to pull. I think I'll adopt a fairly broad policy
for hosting people's topic trees, and merging into xen/master and/or
xen/dom0/hackery if the trees are at least a no-op (ie, don't break things).