Hi, 2012/1/22 David Kastrup <d...@gnu.org>: > Graham Percival <gra...@percival-music.ca> writes: >> With respect to this patch, you have 4 options: >> - modify Patchy to do the appropriate build stuff. >> - recruit somebody else to modify Patchy for you. >> [...] > > [Patchy's automated testing got confused by stale files in its work tree > and will not be accurate in a timely manner. > If you are testing from a Rietveld patch (actually any patch), please use > git apply --index > for applying the patch so that git sees newly added files in the worktree > and will remove them when you do > git reset --hard]
How to modify Patchy? In an old e-mail i've found a link to what looks like Patchy source code https://github.com/gperciva/lilypond-extra/blob/master/patches/compile_lilypond_test.py and i'm preparing a patch addressing David's advice, but i haven't found how patches for Patchy are announced, reviewed and pushed. Do i need to create a github account? cheers, Janek _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
