On 14/02/14 06:42, David Kastrup wrote:
Thomas Morley <[email protected]> writes:
Regarding the snippet:
Because it is _not_ tagged docs I'd simply delete it.
Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
one should just take them from Documentation/snippets/new (if they
required changes more than running convert-ly).
What I suggest is that instead of doing this piecemeal
(one-at-time-as-you-find-them), make a list of the snippets that you are
having issues with, then provide them to the group enmasse (use the link
or if possible use the name of the snippet - Changing stems direction
without affecting rests - for example, as that makes it quicker to find
in git and remove them all at once.
Else all that will happen is that you'll end up breaking doc builds
unexpectedly as each time you make a change in the snippets/new
directory you have to run the python script and then resubmit a change
to git based on that. It will get very tedious.
Once you have a list, then we can make a tracker and we make the
necessary changes in one hit (or as little 'hits' as possible).
Regards
James
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
