Merge Window closed, submitting patches?
Recently got into the habit of making very simple coding style changes in staging. It's basic, but it is a gentle introduction to the process involved in submitting patches to the kernel. So the merge window is now closed and I have submitted a few patch sets, the first not knowing that the window was closed, and the second wrongly thinking that the window had reopened. My question is about what to do during the closed window? I don't think I should submit patches as I assume I'll create a backlog for the maintainer who'll possibly be flooded when the window re-opens. Similarly I could create patches but not send them until the window re-opens, but again I'll just be creating a backlog. So I guess I should just be patient and find something else to do for a while, but thought I'd ask. I have tried to find the answer to this but haven't found one. jwhitmore
On 26 August 2018 at 15:36 John Whitmore <arigead@gmail.com> wrote:
My question is about what to do during the closed window? I don't think I should submit patches as I assume I'll create a backlog for the maintainer who'll possibly be flooded when the window re-opens. Similarly I could create patches but not send them until the window re-opens, but again I'll just be creating a backlog.
Just keep going. The maintainers will keep a queue of patches and then try to apply them in order when the merge window -rc1 is released for the next one. Worse cases would be that the patches will no longer apply (in which case, a V2 will be needed) or, if you haven't heard anything for a while after the -rc1, then a patch RESEND should do the trick. Hope that helps, Justin.
On Sun, Aug 26, 2018 at 03:47:32PM +0100, Justin Skists wrote:
On 26 August 2018 at 15:36 John Whitmore <arigead@gmail.com> wrote:
My question is about what to do during the closed window? I don't think I should submit patches as I assume I'll create a backlog for the maintainer who'll possibly be flooded when the window re-opens. Similarly I could create patches but not send them until the window re-opens, but again I'll just be creating a backlog.
Just keep going. The maintainers will keep a queue of patches and then try to apply them in order when the merge window -rc1 is released for the next one.
Worse cases would be that the patches will no longer apply (in which case, a V2 will be needed) or, if you haven't heard anything for a while after the -rc1, then a patch RESEND should do the trick.
Hope that helps, Justin.
Thank you, yes that helps!
participants (2)
-
John Whitmore -
Justin Skists