From: David Miller <davem@davemloft.net>
To: Ian.Campbell@eu.citrix.com
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org,
xen-devel@lists.xensource.com, jeremy@goop.org,
herbert@gondor.apana.org.au, konrad.wilk@oracle.com,
romieu@fr.zoreil.com, shemminger@vyatta.com, mirqus@gmail.com
Subject: Re: [GIT/PATCH v5] xen network backend driver
Date: Mon, 14 Mar 2011 15:22:55 -0700 (PDT) [thread overview]
Message-ID: <20110314.152255.68135182.davem@davemloft.net> (raw)
In-Reply-To: <1300141060.32696.36.camel@localhost.localdomain>
From: Ian Campbell <Ian.Campbell@eu.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.
next prev parent reply other threads:[~2011-03-14 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 14:27 [GIT/PATCH v5] xen network backend driver Ian Campbell
2011-03-14 18:40 ` Ben Hutchings
2011-03-14 19:30 ` Ian Campbell
2011-03-14 20:23 ` David Miller
2011-03-14 22:17 ` Ian Campbell
2011-03-14 22:22 ` David Miller [this message]
2011-03-15 7:09 ` Ian Campbell
2011-03-15 10:06 ` Ian Campbell
2011-03-14 18:57 ` Eric Dumazet
2011-03-14 19:33 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110314.152255.68135182.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ian.Campbell@eu.citrix.com \
--cc=bhutchings@solarflare.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@vyatta.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).