lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: parenthesizeStencil and bracketifyStencil (issue 6397043)


From: Phil Holmes
Subject: Re: parenthesizeStencil and bracketifyStencil (issue 6397043)
Date: Sat, 14 Jul 2012 11:42:34 +0100

----- Original Message ----- From: "Thomas Morley" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>; <address@hidden>
Sent: Friday, July 13, 2012 11:13 PM
Subject: Re: parenthesizeStencil and bracketifyStencil (issue 6397043)


2012/7/13 Phil Holmes <address@hidden>:
(...)
So - if your changes will break the snippet, but will only work in in future
versions, copy the snippet to snippets/new and update it there.

Copy or cut and paste?
What about
%% and then run scripts/auxiliar/makelsr.py
?

-Harm


Copy will be fine. makelsr uses the version in /new to overwrite the tarball version. It's not always _necessary_ to run makelsr, since if you create a patch with a new snippet in /new, the LSR-meister (i.e. me) will at some point run makelsr and therefore update snippets. However, if the changes break the snippet completely, and this breaks make doc, then you should run makelsr and then also include the new version of the snippet in /snippets in the patch.

Hope this makes some sense.  It's difficult to explain.

--
Phil Holmes



reply via email to

[Prev in Thread] Current Thread [Next in Thread]