On Wednesday 06 April 2005 2:26 pm, Greg KH wrote: > I'm thinking of doing something like the following: > > - provide raw quilt directory of patches (like the directory > above has in it.) > - nightly provide a patch against the latest kernel tree for the > different projects I keep track of (usb, i2c, pci, driver > core, everything-and-the-kitchen-sink, etc.) This patch will > be made by applying a subset of the above patches (delineated > by proejct type), and will probably be what ends up in the -mm > releases. > > Sound good to start with?
Sounds like a plan. Though what will the "latest kernel tree" be? These answers are needed all up the stack ... and for all the arch trees too. No more "2.6.X-rcY-bkZ" snapshots, for example. For now I suppose "latest" can mean "2.6.12-rc2", at least for USB. I'm going to have to figure out what to do with the various patches that for whatever reason don't seem "ready for mainline". One of several nice things about BK is that it's easy to push things to some bkbits.net address, so anyone can get them. A new scheme will be needed; or maybe more folk will use the sf.net patch databases. All those random BK trees will either get pushed towards mainline, abandoned, or in some cases turned into even more layered patchsets. - Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
