Le vendredi 20 novembre 2009 à 14:56 +0000, Graham Percival a écrit : > 1) cd Documentation; make doc > 2) go cook dinner or read slashdot or catch up on emails or > whatever > 3) if it fails, complain on -devel. If it succeedes, then commit > the changes you want to test. > 4) touch Documentation/changed-manual.tely > 5) cd Documentation; make doc > 6) go cook dinner or read slashdot or catch up on emails or > whatever > 7) if it fails, complain to the person who sent you the patch.
... and add a few minutes for 8) quickly skim through the output (HTML, PDF, and/or Info) to see whether the result looks good; this is not necessary all the time, e.g. it's not absolutely necessary when you edit only plain text. Best, John
signature.asc
Description: Ceci est une partie de message numériquement signée
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
