On 2017/07/10 15:38:52, Carl wrote:
On 2017/07/10 14:09:53, dak wrote: >
https://codereview.appspot.com/326870043/diff/1/Documentation/snippets/changing-partcombine-texts.ly
> File Documentation/snippets/changing-partcombine-texts.ly (right): > >
https://codereview.appspot.com/326870043/diff/1/Documentation/snippets/changing-partcombine-texts.ly#newcode24
> Documentation/snippets/changing-partcombine-texts.ly:24:
\partCombine
> On 2017/07/10 12:50:12, PhilEHolmes wrote:
> > The best way to change snippets is to edit the LSR and then > > follow the CG instructions for transferring those changes over > > to the docs. HTH.
> This is not an option since snippets in the LSR are supposed to be > valid for an older version of LilyPond.
> Instead you have to rely on the convert-ly run that makelsr.py > does.
I understood that the CG also says you can place an edited version of the snippet in Documentation/snippets/new with a lilypond version of the current development version. Is this incorrect?
This is correct but causes significant followup maintenance work as it creates snippet versions maintained separately from the LSR. For things that are successfully covered by convert-ly rules it does not make sense to engage this mechanism. This particularly concerns _bulks_ of snippets. https://codereview.appspot.com/326870043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
