Mark Polesky wrote Friday, July 24, 2009 3:16 AM
One wrinkle is that compiling and testing things with "make doc" is (at the moment) out of the question on the computer that I currently have access to. Which means that I can't definitively prove that my patches don't break anything, even though in some cases (like fixing typos) there shouldn't be a problem.
It is possible to check the syntax of the texinfo docs under Windows by running the file through lilypond-book and texi2html, but this doesn't help with doc string edits.
Let me know if you guys would rather have me skip the proofreading step for trivial patches, but until I hear otherwise, I'll continue to run them through -devel.
Go ahead and push trivial changes to doc strings and the docs themselves. Code changes are a different matter and must be reviewed first. If a commit causes a problem the next person to build LP will either fix it if it is easily fixed or simply revert your change, so as long as the change is trivial no real harm is done. Trevor _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
