Re: BK kernel workflow
From: Jeff Garzik
Date: Mon Oct 25 2004 - 11:40:41 EST
Matthias Urlichs wrote:
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.)
Wrong on all counts.
The right answer is, "bk-netdev conflicts with some other BK tree that's
also not yet in upstream"
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/