[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080220.131530.18314167.davem@davemloft.net>
Date: Wed, 20 Feb 2008 13:15:30 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: jeff@...zik.org
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git patches] net driver fixes
From: Jeff Garzik <jeff@...zik.org>
Date: Wed, 20 Feb 2008 11:55:57 -0500
>
> Note: this is based off of Linus's latest commit
> (5d9c4a7de64d398604a978d267a6987f1f4025b7), since all my previous
> submissions are now upstream (thanks!).
The whole point of my not rebasing net-2.6 is so that you can always
use it as a base.
With what you've giving me now I either have to:
1) Pull in Linus's tree to net-2.6, then pull from you.
2) Pull in directly from you to get it all.
The whole point of my not touching or rebasing net-2.6 is so that
everyonce can simply use it as a base and just keep working relative
to it.
If you have some need for upstream stuff outside networking (f.e.
some ACPI bug prevents interrupts from working or there is some build
failure), you can clone Linus's tree and pull net-2.6 and your driver
bits into there for building and testing.
Thanks for your consideration, I'm trying to show you mine by
giving everyone a relatively stable tree in which all networking
development can occur.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists