"But the fact that I'm going to be (effectively) off-line next week
means that I'm not opening the merge window for 3.13 yet - since I
won't have the bandwidth to really do merges anyway.
That doesn't mean that you can't send me pull request for the merge
window early, of course - maintainers can always send their pull
requests early rather than late, if they have everything lined up and
ready. But if you have some feature that still wants polishing, you
basically get a free week to do that.
So the two-week merge window for 3.13 will start a week from now. You
have an extra week. But that also means that I will be doubly
disappointed in anybody who then leaves their merge request until the
end of that two-week merge window."
Linus is in absolute control of the kernel development -- this works quite well, but if he gets sick or whatever then how quickly and well will the community find a substitute?
From what I saw and of the other core committers could take over his job. If Linus is not merging things, commits are probably just piling up on the repos of the respective subsystem responsible persons.
If you have an easy way to reproduce that could you report a bug about that upstream?
The only way to reproduce it for me is when using a hotel WiFi, which gives a quite narrow window to report bugs/test patches.
Thanks for pointing that out! Good to know I won't need that work around in the future. I need to get back into this, got a couple of graphics cards lying dormant in a server just begging to be passed through to guests!
In case anyone else is curious, DRM in the kernel stands for Direct Rendering Manager [1]. It has nothing to do with the DRM that's usually discussed on HN.
The name Direct Rendering Manager has been around since the '90s, since the XFree86 days. So I'm pretty sure this abbreviation predates that of the "bad" DRM.
Linus @ https://lwn.net/Articles/572706/
"But the fact that I'm going to be (effectively) off-line next week means that I'm not opening the merge window for 3.13 yet - since I won't have the bandwidth to really do merges anyway. That doesn't mean that you can't send me pull request for the merge window early, of course - maintainers can always send their pull requests early rather than late, if they have everything lined up and ready. But if you have some feature that still wants polishing, you basically get a free week to do that. So the two-week merge window for 3.13 will start a week from now. You have an extra week. But that also means that I will be doubly disappointed in anybody who then leaves their merge request until the end of that two-week merge window."
Linus is in absolute control of the kernel development -- this works quite well, but if he gets sick or whatever then how quickly and well will the community find a substitute?