From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] Kvmppc git tree is ready
Date: Mon, 28 Jan 2008 16:51:45 +0000 [thread overview]
Message-ID: <1201539105.8969.10.camel@basalt> (raw)
In-Reply-To: <ABF87B0B6A38C0458E319AC973ED68AEB8356C@zch01exm26.fsl.freescale.net>
On Tue, 2008-01-29 at 00:34 +0800, Zhang Wei wrote:
> Hi, fellows,
>
> We have mail list, we have patches, now we have git tree.
>
> Discussing with Hollis, I created the git tree for our kvmppc
> development.
> We will put new codes on it and prepare patches for Avi to pull.
>
> You can refer to the web view site about it:
> http://zh-kernel.org/gitweb/?p=kvmppc.git;a=summary
>
> You can clone it by command:
> git clone http://zh-kernel.org/scm/kvmppc.git
>
> I might miss some of your patches. If you can rebase it to the new top
> tree and re-send out, I'll be very appreciative.
The patch that you've imported from me ("[PATCH] PowerPC 440 KVM
implementation.") is one version out of date. Because I introduced
significant changes in the patch I sent out Thu, 24 Jan 2008 19:08:32
-0600, many of which obviate some of your e500 patches, it would
probably make more sense for you to rebase the e500 patches you have
committed on top of that...
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next prev parent reply other threads:[~2008-01-28 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 16:34 [kvm-ppc-devel] Kvmppc git tree is ready Zhang Wei
2008-01-28 16:51 ` Hollis Blanchard [this message]
2008-01-29 2:56 ` Zhang Wei
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=1201539105.8969.10.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
/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.