 Home |
Products |
Support |
Community |
News |
xen-merge
[Xen-merge] merging the xen-merge work ?
| To: | xen-merge@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-merge] merging the xen-merge work ? |
| From: | Rik van Riel <riel@xxxxxxxxxx> |
| Date: | Tue, 30 Aug 2005 15:53:34 -0400 (EDT) |
| Delivery-date: | Tue, 30 Aug 2005 19:51:23 +0000 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-merge-request@lists.xensource.com?subject=help> |
| List-id: | xen-merge <xen-merge.lists.xensource.com> |
| List-post: | <mailto:xen-merge@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-merge-bounces@xxxxxxxxxxxxxxxxxxx |
I'm wondering where we should merge the xen-merge work first: into the xenolinux tree for 2.6.13, or into the upstream kernel? At any rate, it would be nice to finally get rid of the sparse trees - those are a pain to merge up to newer kernel snapshots ;) -- All Rights Reversed _______________________________________________ Xen-merge mailing list Xen-merge@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-merge |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-merge] fs/gs handling, Kurt Garloff |
|---|---|
| Next by Date: | Re: [Xen-merge] merging the xen-merge work ?, Chris Wright |
| Previous by Thread: | [Xen-merge] FW: Xen and the Art of Linux/ia64 Virtualization, Magenheimer, Dan (HP Labs Fort Collins) |
| Next by Thread: | Re: [Xen-merge] merging the xen-merge work ?, Chris Wright |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
