Re: GSoC 2020 update, June 5

2020-06-05 Thread Werner LEMBERG
Hello Owen, > This week, I was able to encode the whole note (semibreve) glyph in > its proper SMuFL-encoded spot in the PUA based on .mf log output. > > I also got LilyPond to use a generated Scheme hash table to try to > look up a glyph's SMuFL character code before falling back to the >

GSoC 2020 update, June 5

2020-06-05 Thread Owen Lamb
Hi all, This week, I was able to encode the whole note (semibreve) glyph in its proper SMuFL-encoded spot in the PUA based on .mf log output. I also got LilyPond to use a generated Scheme hash table to try to look up a glyph's SMuFL character code before falling back to the old way. This was

Re: helping with testing resources

2020-06-05 Thread Dan Eble
On May 24, 2020, at 06:51, Jonas Hahnfeld wrote: > > I'm currently researching how GitLab schedules jobs. Unfortunately it > seems to be first-come-first-serve, so no priority for currently online > specific runners. But every runner, if intermittent or not, has a > chance of getting a job

Re: new procedure with GitLab CI

2020-06-05 Thread Jonas Hahnfeld
Am Freitag, den 05.06.2020, 11:00 +0200 schrieb Valentin Villenave: > On 6/4/20, Jean Abou Samra wrote: > > Actually, I had anticipated a long thread full of reactionson bothof the > > above options, but not such a silence. Anyone? (I won't feel offended if > > you find my proposal dumb!) > >

Re: new procedure with GitLab CI

2020-06-05 Thread Valentin Villenave
On 6/4/20, Jean Abou Samra wrote: > Actually, I had anticipated a long thread full of reactionson bothof the > above options, but not such a silence. Anyone? (I won't feel offended if > you find my proposal dumb!) Well, you have to account for the fatigue :-) I’m not knowledgeable enough to