On Wed, 26 Oct 2016 21:14:00 -0200 Mauro Carvalho Chehab <[email protected]> wrote:
> On a very quick look on the document, it seems that the legacy info > there are at this section of the document: > > - Finding it the old way > > IMHO, we can strip that section completely. At least we agree on that part. > The git bisect section is too small to my taste, as, IMHO, the best would > be if it would be telling about the process, e. g. pointing or C/C the > contents of articles like: Too small? Mauro, it's six lines, one of which reads, in its entirety, "have fun" :) The stuff you propose adding is good, but is it really better than saying "read the git-bisect man page"? That page is pretty clear, especially by the standard of git man pages :) > What do you think about the patch below? I double-checked the > "Fixing the bug" part, and what is there makes sense for me. > I changed it a little bit to make it easier for newbies. Not sure; when's the last time the objdump stuff was really relevant to you? I can certainly see the value of a proper "how to debug the kernel" guide, talking about the *many* facilities we have for kernel debugging at this point. This document isn't that. I've dropped my deletion patch from the series for now (will likely apply the rest shortly), but I still think we need to be more willing to dump old stuff that we can't maintain properly. Thanks, jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
