[Trimmed the recipients considerably; there's really no need to keep spamming so many people about this.] On Mon, 19 Jun 2023, Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> wrote: > Not knowing dim I think there is a simple(?) technical solution here: It > only has to make sure that after the pull request from drm-misc to drm > was sent, no new patches are added to the branch that is merged in next. The drm-misc-next and drm-intel-next branches are *always* open to patches, regardless of the merge window. That's not going to change. We never tell people "this is not the right time for your patches" due to the merge window, like some subsystems do. We have separate branches specifically for feeding to linux-next and they serve no other purpose. The tooling tries to push the right thing there, depending on the last pull request cutoff, so that linux-next reflects what it's supposed to, but obviously the tooling doesn't have the smarts to figure out when the last pull request is going to be sent. (Really, humans don't always get that right either, because predicting the future is kind of hard.) Looks like you hit an issue, and although nobody else has complained about this one over the 9 years we've been using dim, it royally confused you. Sorry about that. There's always room for improvement in the tooling, in the process, and in the human communication. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center
