On Thu, Apr 11, 2013 at 05:30:52PM +0200, Wesley W. Terpstra wrote: > Is there a document that describes how to track the progress a patch > makes on its way to a released kernel version? I understand that > subsystem maintainers aggregate changes which then are aggregated in > turn by Linus, but beyond that I have no understanding of the flow. Not really, as each maintainer has a different workflow. For example, my scripts will email you when the patch is applied to my trees with some information as to what is going to happen to it, and where you can find the patch. Other maintainers just do a short "patch applied" email response, and others (and I personally hate this), don't say anything at all and you have to watch and see if your patch ever gets applied anywhere. You might want to look at Documentation/development_model/ for some information on how the overall process works. If you have any questions about it after reading this, be sure to let us know. > Also: Thank you very much for all your help. I've made several kernel > modules over the years, but never submitted any of them for inclusion > because I had the (it seems false) impression that the linux kernel > development process was full of angry people who would make it > unpleasant. > > Glad to learn that this is just a myth! > I will probably contribute more patches in the future. That's good to hear. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
