"Phil Holmes" <[email protected]> writes: [...]
>> But Documentation/snippets is not the baseline. It's pretty much >> completely a generated directory. The baseline is the LSR after running >> convert-ly on it, with Documentation/snippets/new acting as override. >> >> So what you want to be doing is another LSR import from the current LSR >> first. Then one has to check which of Documentation/snippets/new is no >> longer needed and can be removed, and which should be retained and/or >> merged with the LSR. >> >> Unless I totally misunderstand something here. > > > OK. I'll create a new patch with the updated LSR address change > only. However, before running a makelsr run from the LSR, I'll need to > do some further checks on the changes makelsr is making to the > snippets, and preferably get snippets/new in shape. > > Please revert this. Thanks, will do. Basically what you want to end up with, if everything is fine, is that makelsr.py either with a full LSR import (the CG describes how to do it) or just run on its own does not cause a change on top of your finished work any more. With regard to LSR links one probably needs to check whether they are (re-)introduced via makelsr or some other script if one really wants to get rid of the bad links for good. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
