http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/release-work.itexi File Documentation/contributor/release-work.itexi (right):
http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/release-work.itexi#newcode87 Documentation/contributor/release-work.itexi:87: make po-replace Thanks, this is exactly the kind of thing I wanted you to do! However, a few note: the po-replace must happen before the vi command, otherwise the "make po-replace" text will be sent to the vi command when I copy&paste the entire block. Also, how about moving po-replace above the vi, then adding the git commit ... po/lilypond.pot above the vi command as well? That'll make the copy&paste process easier. http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/release-work.itexi#newcode373 Documentation/contributor/release-work.itexi:373: coordinator@@translationproject.org, mentioning lilypond-VERSION.pot I think you already know this, but just to confirm: you know that this isn't part of the regular release process? http://codereview.appspot.com/6195060/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel