Knut Petersen <knut_peter...@t-online.de> writes: > Great. I can reproduce the problem. > > After that I created branch stabletest. stabletest is stable/2.20 with 3 > additional commits cherry-picked commits from master: > > commit 2c7277e0014b8d1d22ef5a1caa69a2f86bcfb964 > commit 430fcf895a49d8159413f194488b8474d4ae6be6 > commit 61d42c83db9abf567da0dcabec50df71d56d2bf9
Well, in reverse order of picking. > That succeeds. As lilypond stable/2.20 needs to be compatible with recent > versions of gs and gub I see no real problem and recommend to cherry-pick the > three patches into stable/2.20. Done. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
