Messages in this thread | | | From | Matthias Urlichs <> | Subject | Re: BK kernel workflow | Date | Mon, 25 Oct 2004 15:01:50 +0200 |
| |
Hi, Greg KH wrote:
> On Tue, Oct 19, 2004 at 11:54:16PM +0200, Paolo Ciarrocchi wrote: >> I know I'm pedantic but can we all see the list of bk trees ("patches >> ready for mainstream" and "patches eventually ready for mainstream") >> that we'll be used by Linus ? > > The -mm releases has these as a big patch, starting with bk-*
Umm, yeah, but it's *one* big patch (or, if you use my -mm import tree from bk://smurf.bkbits.net/linux-2.6.X-rcY-mmZ, one BK pull which has that as a subtree).
Paolo wants to see two distinct ones.
Andrew also does things like
bk-netdev.patch e1000-module_param-fix.patch ne2k-pci-pci-build-fix.patch r8169-module_param-fix.patch
which my mind translates as "there's something stupid, incomplete or outdated in the bk-netdev tree", or "that tree's maintainer should apply these patches. Now." (Ideally, of course, my import script should do the same thing.)
-- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |