linux-next: wireless for-next branches
Hi Stephen,
We are experimenting how we could take "next-next" patches during merge windows and avoid accumulation of patches for the period which is in practice three weeks for wireless patches. To do that could you please change linux-next to pull from wireless trees for-next branches instead of main branches? So the new locations are:
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git for-nextgit://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git for-next
The idea we have is that wireless-next for-next branch is not updated during the merge window and then the "next-next" patches will not be included in linux-next until the merge window has closed.
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Hi Kalle,
Quoted 7 lines · On Fri, 27 May 2022 11:58:03 +0300 Kalle Valo <[email protected]> wrote:
We are experimenting how we could take "next-next" patches during merge windows and avoid accumulation of patches for the period which is in practice three weeks for wireless patches. To do that could you please change linux-next to pull from wireless trees for-next branches instead of main branches? So the new locations are:
Quoted 6 lines
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.gitfor-nextgit://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.gitfor-nextThe idea we have is that wireless-next for-next branch is not updated during the merge window and then the "next-next" patches will not be included in linux-next until the merge window has closed.
OK, I have switched to using those branches.
Signature · 2 lines
Cheers, Stephen Rothwell
Quoted 8 lines · Stephen Rothwell
Quoted 7 lines · On Fri, 27 May 2022 11:58:03 +0300 Kalle Valo <[email protected]> wrote:
We are experimenting how we could take "next-next" patches during merge windows and avoid accumulation of patches for the period which is in practice three weeks for wireless patches. To do that could you please change linux-next to pull from wireless trees for-next branches instead of main branches? So the new locations are:
Quoted 8 lines
Quoted 6 lines
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.gitfor-nextgit://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.gitfor-nextThe idea we have is that wireless-next for-next branch is not updated during the merge window and then the "next-next" patches will not be included in linux-next until the merge window has closed.
OK, I have switched to using those branches.
Great, thank you Stephen. I now took the first patch[1] to wireless-next main branch but you should not see it in for-next branch until the merge window is closed.
Signature · 3 lines
https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches