On Thu, Nov 11, 2010 at 10:25:00AM -0800, Sarah Sharp wrote: > On Mon, Nov 08, 2010 at 12:00:23PM -0800, 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. > > > ... > > If anyone has any questions about this, please let me know. > > How does sending a pull request for a branch based on usb-linus work > when one of the patches needs to be queued for stable? Do I just need > to add the line > > Cc: stable@xxxxxxxxxx > > to the patch, and it will get picked up when you send to Linus? It was > easy before, I'd just Cc stable@xxxxxxxxxx when I sent you the original > patch, but now it's a pull request. Yes, just make sure that the Cc: line is part of the signed-off-by: area of the patch and it will automatically get sent to the stable kernel when it goes to Linus's tree. hope this helps, 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
