| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [GIT/PATCH v5] xen network backend driver
|
To: |
Ian.Campbell@xxxxxxxxxxxxx |
|
Subject: |
[Xen-devel] Re: [GIT/PATCH v5] xen network backend driver |
|
From: |
David Miller <davem@xxxxxxxxxxxxx> |
|
Date: |
Mon, 14 Mar 2011 15:22:55 -0700 (PDT) |
|
Cc: |
jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, herbert@xxxxxxxxxxxxxxxxxxx, konrad.wilk@xxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, mirqus@xxxxxxxxx, romieu@xxxxxxxxxxxxx, bhutchings@xxxxxxxxxxxxxx, shemminger@xxxxxxxxxx |
|
Delivery-date: |
Mon, 14 Mar 2011 15:22:48 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<1300141060.32696.36.camel@xxxxxxxxxxxxxxxxxxxxx> |
|
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> |
|
References: |
<1300131040.32696.23.camel@xxxxxxxxxxxxxxxxxxxxx> <20110314.132355.226777213.davem@xxxxxxxxxxxxx> <1300141060.32696.36.camel@xxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Mon, 14 Mar 2011 22:17:40 +0000
> Would you consider a commit patch which imports the baseline driver as
> is from xen.git (this builds and is functional but needed clean up)
> followed by the cleanup series? I made sure the cleanup part builds and
> works at each step as I went (but I will run through it again to be
> sure).
>
> There is real value (to me at least) in keeping the cleanup separate and
> being able to (even manually) associate the first upstream commit with
> an equivalent point in the historical code.
Do you have any idea what that thing is going to do for poor souls trying
to bisect?
GIT is going to hop in and out of your line of development for any GIT
bisect that traverses any period of time in which those driver commits
exists.
It's too messy.
You can keep your tree online somewhere to publish the history, just
like we do for the old bitkeeper import and similar.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home