Re: Backporting documentation changes?
Jonas Hahnfeld via Discussions on LilyPond development <[email protected]>
| Newsgroups | gmane.comp.gnu.lilypond.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, 2026-08-16 at 17:59 +0000, Werner LEMBERG wrote: > > Here's a list of "currently pending" MRs, should these be > > backported? > > > > !3039 Improve engraving bibliography > > https://gitlab.com/lilypond/lilypond/-/merge_requests/3039 > > At your discretion. It just makes prettier output, fixing only minor > things. Ok, I skipped this merge request. > > > !3044 time-signature-interface: clarify style options > > https://gitlab.com/lilypond/lilypond/-/merge_requests/3044 > > Yes, since Dan mentions 2.26 explicitly. > > > !3053 NR: Use real apostrophe in LilyPond code example > > https://gitlab.com/lilypond/lilypond/-/merge_requests/3053 > > At your discretion. It just makes prettier output. > > > !3070 NR: Document some font selection problems with FontConfig > > https://gitlab.com/lilypond/lilypond/-/merge_requests/3070 > > Yes. > > > !3088 NR: Clarify default metric properties and exceptions > > https://gitlab.com/lilypond/lilypond/-/merge_requests/3088 > > !3096 NR: "Time administration" → "Measures" > > https://gitlab.com/lilypond/lilypond/-/merge_requests/3096 > > I vote yes for both, since Dan's explanations help a lot in understanding > the topics. Thanks for your replies, the rest is backported for stable/2.26.
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRiF4DLRvon1vw5biCcVOmY/6OEDwUCaotRpwAKCRCcVOmY/6OE D0inAQCPpIkqRmbME90Ckgnw18a0hiAmcuYpq7pf9wNULMNIXQEAqBT5XoAJ1ldb CQ1r3zcw4vlFX0jT163sMpnrz4rx1Ag= =Br29 -----END PGP SIGNATURE-----