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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 Mar 2011 15:22:55 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	Ian.Campbell@...citrix.com
Cc:	bhutchings@...arflare.com, netdev@...r.kernel.org,
	xen-devel@...ts.xensource.com, jeremy@...p.org,
	herbert@...dor.apana.org.au, konrad.wilk@...cle.com,
	romieu@...zoreil.com, shemminger@...tta.com, mirqus@...il.com
Subject: Re: [GIT/PATCH v5] xen network backend driver

From: Ian Campbell <Ian.Campbell@...citrix.com>
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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html