Am 12.05.2018 um 09:16 schrieb James Lowe:
Dev team,

Don tacked a patch on the end of an already-fixed issue.

James, they try to fix lilypond 2.18, not 2.20 or master.

2.18 is still insecure.

Knut

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to