Philip Oakley wrote: > From: "Thomas Ackermann" <th.acker@xxxxxxxx> >> (5) Large overlapping with the tutorials. IMHO all of the >> tutorials should be blended into user-manual [...] > I would be a little cautious of your point 5 if it squoze everything into > one overlong document at the expense of losing the shorter documents - one > can't eat a whole melon in one bite ;-) Yes. Once there was a lovely file at Documentation/howto/isolate-bugs-with-bisect.txt explaining how to use "git bisect" to find which commit caused a kernel regression. That it was a small independent file that didn't assume the reader had read much before was very helpful, since it meant people could easily point novices to that page and say "It's easy!" when asking them to track down a bug. Nowadays that content is gracefully included in the user-manual under the heading [[using-bisect]]. But I never point people to it any more; I just write out the steps by hand, to avoid intimidating them. Ideally this content would be in an EXAMPLE or TUTORIAL section of the git-bisect(1) manpage for easier reference. Thanks, Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html