Backporting documentation changes?
Jonas Hahnfeld via Discussions on LilyPond development <[email protected]>
| Newsgroups | gmane.comp.gnu.lilypond.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I just went through the list of merge requests labeled for backporting.
Apologies that it took me that long to get to it, my time for LilyPond
is limited these days...
In the past, I've been hesitant to backport documentation changes,
partly because it's not clear how much they qualify as "fix" and on the
other hand because it results in "outdated" translations (though that's
only French these days). Here's a list of "currently pending" MRs,
should these be backported?
!3039 Improve engraving bibliography
https://gitlab.com/lilypond/lilypond/-/merge_requests/3039
!3044 time-signature-interface: clarify style options
https://gitlab.com/lilypond/lilypond/-/merge_requests/3044
!3053 NR: Use real apostrophe in LilyPond code example
https://gitlab.com/lilypond/lilypond/-/merge_requests/3053
!3070 NR: Document some font selection problems with FontConfig
https://gitlab.com/lilypond/lilypond/-/merge_requests/3070
!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
Jonas
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRiF4DLRvon1vw5biCcVOmY/6OEDwUCaoH0zQAKCRCcVOmY/6OE D+uMAP4oBXKj5w7hUojTPlNxuq21MF+UM0DhC1mc2b6VvR+STAEAnESr3k+B7Qcp yfutCoXw4myiwNIeR4vEwGglON+pfAo= =cqtZ -----END PGP SIGNATURE-----