This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [GIT/PATCH v5] xen network backend driver

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

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