On Tue, Nov 09, 2010 at 02:00:43PM -0800, Sarah Sharp wrote: > On Tue, Nov 09, 2010 at 10:01:28AM +0200, Felipe Balbi wrote: > > On Mon, Nov 08, 2010 at 02:00:23PM -0600, Greg KH wrote: > > >Hi all, > > > > > >After a discussion at the kernel summit last week, Linus expressed a > > >strong preference for the subsystem maintainers to start using git, and > > >for them to start accepting git pulls from the people that they trust as > > >well. > > > > > >So, I'm going to try to switch over to using git for development and to > > >send patches to Linus directly. My git tree is now at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git > > > > > >There are two branches in there: > > > usb-next - this is what should show up in the linux-next tree > > > usb-linus - this is what I'm wanting to push to Linus for this > > > major release. > > > > Thanks, that actually makes my life a lot easier :-) To be sure my > > patches where applied, I only to check two branches from you, no need > > for scripting around git quiltimport :-) > > > > To send pulls, I'll always base of Linus' most recent tag. > > Hmm, but if you're sending patches for linux-next (i.e. not for the > current rc), then don't you want to base off of Greg's usb-next tree? Yes, please do that, otherwise I'll get extra merges that I do not need, and Linus does not want. I'll merge to Linus's tree ever -rc or so, only if needed for the -next branches. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
