On Sun, 11 Oct 2020 17:59:16 -0700 Alexei Starovoitov wrote: > Hi BPF developers, > > The merge window has just opened. > Which would typically mean that bpf-next is closing, > but things are going to be a little bit different this time. > We're stopping to accept new features into bpf-next/master. > The few pending patches might get applied and imminent pull-req into > net-next will be sent. > After that bpf-next/master will be frozen for the duration of the merge > window, > but bpf-next/next branch will be open for the new features. > > So please continue the BPF development and keep sending your patches. > They will be reviewed as usual. > After the merge window everything that is accumulated in bpf-next/next > will be applied to bpf-next/master. > Due to merge/rebase sha-s in bpf-next/next will likely be unstable. > > Please focus on fixing bugs that may get exposed during the merge window. > The bpf tree is always open for bug fixes.
FWIW for CIs switching between bpf-next/next and bpf-next/master could be somewhat fragile. Since bpf-next/master is frozen during the merge window, why not apply the patches there?
