All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: Yuji Shimada <shimada-yxb@necst.nec.co.jp>,
	Xen Developers <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] [Xend] Fix HVM PCI hot removal failure
Date: Tue, 28 Apr 2009 11:38:24 +0100	[thread overview]
Message-ID: <49F6DCA0.3080700@eu.citrix.com> (raw)
In-Reply-To: <49F6CD74.3020008@intel.com>

Zhai, Edwin wrote:

> 
> Keir Fraser wrote:
>>  On 28/04/2009 09:18, "Zhai, Edwin" <edwin.zhai@intel.com> wrote:
>>
>>> Sorry, I neglected this patch:(
>>>
>>> Do we have plan to improve the coexistence of qemu and xen?
>>> You know, sometimes 2 coupled repos make debug difficult given that qemu
>>> has more and more features(hotplug, power). How about adding a bridge
>>> between qemu's git and xen's hg, so that all the changes can be tracked
>>> easily.
>>  How might that work?
> 
> Just my thoughts, not sure if it's workable:)
> * Ian maintains his git repo background, other developers just see a
>   hg repo including qemu
> * Keep sync between git qemu and hg qemu:
>   1. Any patches including qemu changes go into git repo
> automatically. Can scripts do this?
>   2. When rebase qemu, Ian generate a big patch against previous git
> repo, then push it back to hg repo.
> 
> I have no idea of current qemu rebase process, not sure if any extra
> work load needed. Ian can comment.
> 

A two way synchronization between the qemu hg mirror and the qemu git
repo would mean trouble.

Maybe we could find a way to mirror the qemu git repo inside the
xen-unstable hg repo, but it would still just a mirror.

  reply	other threads:[~2009-04-28 10:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  7:34 [PATCH] [Xend] Fix HVM PCI hot removal failure Zhai, Edwin
2009-04-28  7:52 ` Keir Fraser
2009-04-28  8:18   ` Zhai, Edwin
2009-04-28  9:17     ` Keir Fraser
2009-04-28  9:33       ` Zhai, Edwin
2009-04-28 10:38         ` Stefano Stabellini [this message]
2009-04-29 15:41           ` Repositories and build system Ian Jackson
2009-04-29 16:38             ` Dan Magenheimer
2009-04-29 16:56               ` Ian Jackson
2009-04-29 17:40                 ` Dan Magenheimer
2009-04-29 18:06                   ` Keir Fraser
2009-05-07 16:51                   ` Stefano Stabellini
2009-05-07 17:00                     ` Brendan Cully
2009-05-07 18:17                       ` Keir Fraser
2009-04-28 12:17         ` [PATCH] [Xend] Fix HVM PCI hot removal failure Keir Fraser

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=49F6DCA0.3080700@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=edwin.zhai@intel.com \
    --cc=shimada-yxb@necst.nec.co.jp \
    --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.