 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] separate components and broken out patches
| To: | "Muli Ben-Yehuda" <mulix@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] separate components and broken out patches |
| From: | "Magnus Damm" <magnus.damm@xxxxxxxxx> |
| Date: | Tue, 4 Apr 2006 15:50:33 +0900 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Mon, 03 Apr 2006 23:50:52 -0700 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LtphD4o/ytJahvZbjtToI5HnLh0f4fgPsNGJZMb4/sIW8vJ6EpCIqJmv7Q24YrLKVfmlsPAA2QlKzRf4OemWXHtfZ4xRa14fdAfC6q4gV3ottHhw8FfBnqQcjR2P8Fuy+B/b92Zyfu13N6+he8iRdRk6p8MoIleT7+Gr0F/YmaY= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20060404052937.GH20709@xxxxxxxxxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <aec7e5c30604032009n2cdfaac7u4f65039326dfe389@xxxxxxxxxxxxxx> <20060404052937.GH20709@xxxxxxxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
On 4/4/06, Muli Ben-Yehuda <mulix@xxxxxxxxx> wrote: > On Tue, Apr 04, 2006 at 12:09:53PM +0900, Magnus Damm wrote: > > > So to make my kernel work easier I've hacked on breaking out code from > > the xen-unstable tree into three separate components: > > > > - kernel > > - hypervisor > > - tools > > Just a heads up, in case you aren't aware of it, there's an hg kernel > tree that's cloned from the upstream kernel that you can use to work > on the kernel in the comfort of ... an hg tree. I use it for all of my > Xe kernel work and it's infinitely better (for me) than the > sparse/patches combination. The tree is at > http://xenbits.xensource.com/linux-2.6-xen.hg. Oh, excellent! That's much nicer IMO. Thanks for pointing that out! / magnus _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] separate components and broken out patches, Muli Ben-Yehuda |
|---|---|
| Next by Date: | Re: [Xen-devel] Does dom0 see all physical processors? (RE: [Xen-ia64-devel] SAL INFO virtualization), Keir Fraser |
| Previous by Thread: | Re: [Xen-devel] separate components and broken out patches, Muli Ben-Yehuda |
| Next by Thread: | RE: [Xen-devel] Does dom0 see all physical processors? (RE: [Xen-ia64-devel] SAL INFO virtualization), Tian, Kevin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
