On Mon, Jan 02, 2012 at 09:31:54PM +0000, lilyp...@googlecode.com wrote: > > I did makelsr.py to test it compiled, but figured that reviewing > such a patch 'visually' might be tedious if there are lots of other > files changed.
True. But if you committed a local makelsr build to git first, then did your work and did another makelsr run, you'd only get the single file that you'd just edited. However, there's a lot of confusion about LSR since we haven't had regular updates in a while, so this is understandable. It will get sorted out in a few days or weeks. > But I meant to post the next patch identical as the initial but with > makelsr.py 'on top' (if you see what I mean) so I could push it (and > patchy would not complain). ok, that would also work. Cheers, - Graham _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
