Heikki, you wrote Friday, January 08, 2016 4:18 PM > I still managed (like I always seem to do when I run git-cl with > several months having passed since the last time...) to fail to submit > a patch with git-cl fully successfully (*), so I had to create a new > issue for the tracker (https://sourceforge.net/p/testlilyissues/issues/ > 4730/) manually. I'm sorry if I didn't get the values of all metadata > fields right when creating the issue - I'd be grateful for any help > whether something still needs to be fixed there.
Only the Owner field was missing, so I added your username, and Accepted the Issue. > (*) Failing with git-cl was simply my own fault, as I didn't anticipate > (remember) that git-cl would need to open a web browser in the middle > of the patch submission procedure - this didn't work well as I wasn't > logged on in a GUI session, and had to abort the script. Trevor _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
