Re: Merge Window closed, submitting patches?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Aug 26, 2018 at 03:47:32PM +0100, Justin Skists wrote:
> 
> > On 26 August 2018 at 15:36 John Whitmore <arigead@xxxxxxxxx> 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!

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]

  Powered by Linux