James <pkx1...@gmail.com> writes: >> Actually 2.16 is what we want, so we get lucky here. But the point is >> that most snippets will not be what is wanted. What one can do for any >> particular snippet is something like >> >> git log -S '\version "2.16.0"' -p >> Documentation/snippets/new/chant-or-psalms-notation.ly >> >> which shows when and how the snippet passed into 2.16.0 and beyond it. > > What would one be looking for as such when looking at these snippets > found in git log?
Well, the above is the "optimum case". It actually passed through a 2.16.0 state. Maybe it's more realistic to just omit the -S option and look at the whole history of a snippet. The point is to see at which point of time the snippet stopped being declared fit for 2.16. Let's say that it was commit 13da8b27aabc5d5a752d00ed1e2b99ad20f0f264, so we want the one before that, appending a ~1 to the commit id. You can then use something like git show 13da8b27aabc5d5a752d00ed1e2b99ad20f0f264~1:Documentation/snippets/new/chant-or-psalms-notation.ly to get that snippet. If it isn't at all in Documentation/snippets/new, then it should convert cleanly with convert-ly (unless that snippet just continued to compile but stopped doing what it should, and nobody noticed so far in our documentation). -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
