Thorsten Leemhuis <linux@xxxxxxxxxxxxx> writes: > Add a text explaining how to quickly build a kernel, as that's something > users will often have to do when they want to report an issue or test > proposed fixes. So I think the time has come to apply this. I did have one final thought, though... In the v2 discussion, you said: > Be warned, if it works I might do the same for "reporting issues". ;) > But let's first see how this goes (and if we get any feedback to be able > to tell if this experiment worked). This caused me to wonder if we shouldn't create a new book called "tutorials" for this kind of stuff, with an explicit proviso that a more web-oriented approach is OK in that section? Tutorial documentation *is* quite different from reference material, but we've really made no effort to treat the two differently so far. Thoughts? Thanks, jon
