On Mon, 15 Jul 2013 19:34:44 -0400 Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx> wrote: > The last mainline release of a v2.6.x kernel was back in May 2011. > Here we update references to be 3.x based, which also means updating > some dates and statistics. Ccing the author of the document never hurts :) I actually went through this exercise a while back, but somehow never got around to sending the changes out into the world. Easily distracted, I guess. Anyway, you can put my Acked-by on your changes if you like. > On a similar note, I was thinking about the recent thread on linux-next > where we were indicating that people shouldn't rebase linux-next content > on a whim, and that new devel (vs. bugfix) content shouldn't appear in > the linux-next content during the merge window. There is no question > that the linux-next process is integral to the main flow of patches to > mainline, so I think Documentation/development-process/2.Process (the > same file) should also capture those points in the linux-next section. > Do you have some pre-canned text we can insert there, or should I draft > something up for you to review? Seems useful, I could also try to help with this if you run out of steam. I'd be more inclined to put it into section 7, though, since it's the sort of thing early-stage developers don't normally need to worry about. Thanks, jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
