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 13:23:55 -0700 (PDT) [thread overview]
Message-ID: <20110314.132355.226777213.davem@davemloft.net> (raw)
In-Reply-To: <1300131040.32696.23.camel@localhost.localdomain>
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
Date: Mon, 14 Mar 2011 19:30:40 +0000
> On Mon, 2011-03-14 at 18:40 +0000, Ben Hutchings wrote:
>> I know you have asked for this to be pulled, in order to retain its
>> history, but I'm not sure that David Miller will do this unless the
>> driver is at least buildable at each stage in the history. (However,
>> given that the driver wouldn't be enabled before it's added, I'm not
>> sure it matters in this case.)
>
> I think it should be, at least from the second commit onwards (modulo
> any mistakes made in the past).
I don't want to retain all of that history, there are so many broken
points in the history that the only thing you can do is go back and
add Kconfig commits to depend the driver upon BROKEN, and that in effect
changes the history devalueing it even further.
I just want one patch that adds the driver in it's most current state,
and that's all.
Thanks.
next prev parent reply other threads:[~2011-03-14 20:23 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 [this message]
2011-03-14 22:17 ` Ian Campbell
2011-03-14 22:22 ` David Miller
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.132355.226777213.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).