net-next is OPEN...
Do it, to it.
net-next is OPEN...
You know the drill... http://vger.kernel.org/~davem/net-next.html
net-next is OPEN...
You all know the drill: http://vger.kernel.org/~davem/net-next.html Now, let's see if you guys can avoid drowning me all at once this time :-)
net-next is OPEN....
I know you can crush me with your barrage of patches, let's do it!
net-next is OPEN...
http://vger.kernel.org/~davem/net-next.html
net-next is OPEN
Tell your friends. http://vger.kernel.org/~davem/net-next.html
net-next is OPEN
I know you are all chomping at the bit to bomb me with net-next changes. :-)
net-next is OPEN
I've merged 'net' into 'net-next' and applied a bunch of pending stuff. Fire at will...
net-next is OPEN
However, I'll be travelling most of the day tomorrow so please be gentle. :-)
Re: net-next is OPEN
From: Sergei Shtylyov sergei.shtyl...@cogentembedded.com Date: Thu, 9 Jul 2015 14:49:34 +0300 Hello. On 7/8/2015 11:30 PM, David Miller wrote: Please feel free to bombard me with net-next changes, which some of you have been doing already ;-(, as net-next is now open. Hm, I pulled and didn't see 4.2-rc1 tag. Is it normal? Why does it have to be there? I build net-next by pulling net into net-next. Since 'net' is based upon Linus's tree before he added that tag there is no reason for it to have that tag at all. I really have no idea why you expect it to be there. -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: net-next is OPEN
On 07/09/2015 08:40 PM, David Miller wrote: Please feel free to bombard me with net-next changes, which some of you have been doing already ;-(, as net-next is now open. Hm, I pulled and didn't see 4.2-rc1 tag. Is it normal? Why does it have to be there? I thought your pause during the merge window is caused by you wanting for -rc1 tagging in order for the possible conflicts to be resolved... I build net-next by pulling net into net-next. Well, that merge you do quite routinely. :-) Since 'net' is based upon Linus's tree before he added that tag there is no reason for it to have that tag at all. I really have no idea why you expect it to be there. I then don't quite understand why you close net-next during the merge window and beyond. WBR, Sergei -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: net-next is OPEN
From: Sergei Shtylyov sergei.shtyl...@cogentembedded.com Date: Thu, 09 Jul 2015 20:48:36 +0300 I then don't quite understand why you close net-next during the merge window and beyond. Because when 1700+ changes are committed from us to Linus's tree we should be focused on fixing regressions and fallout from that rather than reviewing new features. Plus, frankly, I'm exhausted during the merge window, and the last thing I need is a backlog of several hundred patches targetting net-next to worry about. -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: net-next is OPEN
Hello. On 7/8/2015 11:30 PM, David Miller wrote: Please feel free to bombard me with net-next changes, which some of you have been doing already ;-(, as net-next is now open. Hm, I pulled and didn't see 4.2-rc1 tag. Is it normal? Thanks. WBR, Sergei -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
net-next is OPEN
Please feel free to bombard me with net-next changes, which some of you have been doing already ;-(, as net-next is now open. Thanks. -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
