On Wed, 2009-06-10 at 15:53 -0600, Gary Thomas wrote: > Trying to understand the process (in preparation for any patches > I may want to push upstream) - how can this be too late for 2.6.31? > 2.6.30 just came out today...
I'm taking the liberty to reply to the list here because I think more people need to understand that problem :-) Because the process is such that new features can only be merged during the 2 weeks merge window, which started ... yesterday. Also, it's frowned upon to have lots of new stuff close to the end of the merge window. The idea is that stuff to go into 2.6.31 should have essentially been ready to merge -before- the merge window opens, ie, before 2.6.30 is released, for us maintainers to be ready to push things out when the merge window open and spend that time sorting out collisions & conflicts, -not- reviewing new features that have been sent way too late. In addition, before being merged, patches should generally be post long in advance since they are likely to go through several revisions as people review and comment on them. This process must happen long before the patch is queued up for the actual merge. So when the merge window opens, it's too late to have your patch be submitted for the first time. Patches that have been submitted a while ago and just didn't make it yet into my "next" branch due to my own lazyness are generally fine. Bug fixes too, at least until -rc3 or -rc4, after which only major bug fixes and regressions are accepted. Cheers, Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev