In message <[email protected]>, Per Buer writes:
>I think the tutorial only should cover the basics). I disagree, we want the tutorial to help people as much as possible, so there is no particular "basics vs advanced" border we should respect. In fact, if we want to push ESI adoption, we probably need to have the tutorial explain it. We can add it later, doesn't have to be now. >I suggest we convert the existing troff >pages into reStructuredText. Given how seldom man-pages change, and how seldom people change them to reflect local hacks, I would simply say build the man pages if we have the tools, if not, too bad. Make dist should probably complain if they are not made though. I totally agree with Tollef on checking in generated files, we should minimize that where we sensibly can[1] Poul-Henning [1] The main reason to check in the VCC files generated by Tcl was Tcl's rarity, now that we use python, I'm open to generate them at compiletime. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ varnish-dev mailing list [email protected] http://lists.varnish-cache.org/mailman/listinfo/varnish-dev
