|
|
![](http://www.xen.org/images/globals/pixel.gif) |
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: git repository for SR-IOV development?
To: |
Greg KH <greg@xxxxxxxxx> |
Subject: |
[Xen-devel] Re: git repository for SR-IOV development? |
From: |
H L <swdevyid@xxxxxxxxx> |
Date: |
Thu, 6 Nov 2008 11:58:25 -0800 (PST) |
Cc: |
randy.dunlap@xxxxxxxxxx, Xen-devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>, grundler@xxxxxxxxxxxxxxxx, achiang@xxxxxx, matthew@xxxxxx, linux-pci@xxxxxxxxxxxxxxx, rdreier@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, jbarnes@xxxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, Yu Zhao <yu.zhao@xxxxxxxxx>, kvm@xxxxxxxxxxxxxxx, mingo@xxxxxxx |
Delivery-date: |
Thu, 06 Nov 2008 11:58:50 -0800 |
Domainkey-signature: |
a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=FBnuS7DoIwzwn4chbm/laIZ/QKRgcV/ODsaOXJ/l5Ntpfr9L/cYxeVFz5i+HEtNi9VZIGFJYEusyGhqhpbK5xK9tF3ij7BB+LpNYZSAR4H45viXyzTeZdMTwtVRqP3ezZGDHTpcZ5gDfdMUjE/C10wPTOyguxmEzTRMJ/XM2o54=; |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20081106165914.GA13476@xxxxxxxxx> |
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
Reply-to: |
swdevyid@xxxxxxxxx |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
--- On Thu, 11/6/08, Greg KH <greg@xxxxxxxxx> wrote:
> On Thu, Nov 06, 2008 at 08:51:09AM -0800, H L wrote:
> >
> > Has anyone initiated or given consideration to the
> creation of a git
> > repository (say, on kernel.org) for SR-IOV
> development?
>
> Why? It's only a few patches, right? Why would it
> need a whole new git
> tree?
So as to minimize the time and effort patching a kernel, especially if the tree
(and/or hash level) against which the patches were created fails to be
specified on a mailing-list. Plus, there appears to be questions raised on
how, precisely, the implementation should ultimately be modeled and especially
given that, who knows at this point what number of patches will ultimately be
submitted? I know I've built the "7-patch" one (painfully, by the way), and
I'm aware there's another 15-patch set out there which I've not yet examined.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Re: git repository for SR-IOV development?,
H L <=
|
|
|
|
|