"Scott Chacon" <schacon@xxxxxxxxx> writes: > The book is basically a fork of all three of the guides I mentioned > (User Manual and both Tutorials), and with the scope and goals I > currently have in mind, will not be kept in sync - it's just not going > to be possible. I think in the end, the goals of the texts are so > very different that sections it will simply not make sense to try to > keep them in sync in some sort of automated fashion. That's one of > the reasons why I choose Markdown - I saw no need to use asciidoc, as > the book will not be shipped around with Git or built using the same > processes, and I had no need for the advantages of asciidoc in my > project. I don't think it makes much sense to have the book be a man > page at all. > > However, I will watch the manual and guides and try to incorporate > changes to them as appropriate, and I will likely have some updates to > them myself as I've been more closely scrutinizing them. If that is the approach you decided for your book, I am Ok with that. Not that you need my blessing to do your own book. It was unclear what your goals were, and if one of the goals were to keep the hassle of maintaining shared materials in both manuals up-to-date, choice of markdown seemed suboptimal to me, hence my comments. Thanks. ... /me goes back to work after lunch break ... -- 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
