On Wed, Jan 31, 2007 at 05:37:07PM -0500, Greg Freemyer wrote: > On 1/31/07, Greg KH <greg@xxxxxxxxx> wrote: > >On Wed, Jan 31, 2007 at 11:18:10PM +0100, Javi Roman wrote: > >> Please I have a question about development process, I'm going to focus > >> the attention over wireless development. > >> > >> If I want to begin to hack with wireless kernel code, my first step > >> have to be to do a git pull against linville/wireless-dev.git > >> (Linville's wireless networking development tree). When I'm ready to > >> send a patch I have to send to Linville, in turn Linville will send > >> one to Jeff Garzik (jgarzik/netdev-2.6.git), and the following will be > >> to send patchs to Andrew Morton (he has not -mm git tree), and the > >> last step is to commit with Linus git tree (torvalds/linux-2.6.git). > >> > >> Me -> Linville -> Garzik -> Morton -> Linus > >> > >> is that hierarchy correct? > > > >Yup. > > > I'm a little surprised. > > In libata, Garzik's tree gets automatically pulled by Morton for -mm > testing but when Garzik is satisfied with a patch, he sends it to > Linus directly. So for libata it is: > > Patch Author -> Garzik -> Morton (Auto-pull) > -> Linus (At the request of Garzik) Ah, good catch, yes, you are correct. Jeff's trees automatically show up in -mm through Andrew, but to get to Linus he asks Linus to pull from his tree, going around Andrew. Either way, you don't have to do any extra work once Linville has accepted your patch :) thanks, greg k-h -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
