All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: Keir Fraser <keir@xensource.com>
Cc: Guy Zana <guy@neocleus.com>,
	xen-devel@lists.xensource.com, "Kay,
	Allen M" <allen.m.kay@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: Merging PCI pass-through code
Date: Mon, 4 Jun 2007 21:43:49 +0300	[thread overview]
Message-ID: <20070604184349.GG4556@rhun.ibm.com> (raw)
In-Reply-To: <C2899D95.FECE%keir@xensource.com>

On Mon, Jun 04, 2007 at 10:44:37AM +0100, Keir Fraser wrote:
> On 3/6/07 17:52, "Guy Zana" <guy@neocleus.com> wrote:
> 
> > Since both Neocleus' solution & Intel's solution have overlapping
> > implementations, we should determine what should stays and what goes.
> > There is a question on how should we do the merge?
>
> I like the idea of a separate tree, just for the short term, as a
> shared workspace for merging and development and bug fixing. I can
> arrange to create a new repo called xen-hvm-directio.hg (or a better
> name if you can think of one)? From the list of points below it
> sounds like both sets of patches need some work, quite apart from
> the required merging. Would this method of development suit
> everyone?

Fine by me, provided the end result still shows up on the list for
review before it gets pulled. I do think however that a shared tree
will only be useful if there will be a gate-keeper who will decide
what goes in and what doesn't (based on consensus ). And once there
are bits of the patches that everyone agrees should go in, they could
just go to xen-unstable directly and skip the merge tree...

Cheers,
Muli

      reply	other threads:[~2007-06-04 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 16:52 Merging PCI pass-through code Guy Zana
2007-06-04  9:44 ` Keir Fraser
2007-06-04 18:43   ` Muli Ben-Yehuda [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=20070604184349.GG4556@rhun.ibm.com \
    --to=muli@il.ibm.com \
    --cc=allen.m.kay@intel.com \
    --cc=guy@neocleus.com \
    --cc=keir@xensource.com \
    --cc=kevin.tian@intel.com \
    --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.