On Sat, Jul 27, 2019 at 1:50 AM Knut Petersen wrote:
> But as 32-bit works in principle, with the help of qemu it is time to try
> to build the windows installer:
>
> bin/gub mingw::lilypond-installer
>
> If that succeeds there will be a lilypond-2.21.0-1.mingw.exe in ./uploads.
It appears tools:
James writes:
> Hello,
>
> On 27/07/2019 10:10, David Kastrup wrote:
>> James writes:
>>
>>> On 26/07/2019 19:36, David Kastrup wrote:
...
I run Patchy when I notice something went to staging. Due to its cost,
I tend to abort it when I discover someone else pushing before me.
>>>
Hello,
On 27/07/2019 10:10, David Kastrup wrote:
James writes:
On 26/07/2019 19:36, David Kastrup wrote:
...
I run Patchy when I notice something went to staging. Due to its cost,
I tend to abort it when I discover someone else pushing before me.
So it would appear that your repository (an
James writes:
> On 26/07/2019 19:36, David Kastrup wrote:
>> ...
>> I run Patchy when I notice something went to staging. Due to its cost,
>> I tend to abort it when I discover someone else pushing before me.
>>
>> So it would appear that your repository (and probably that of Knut) have
>> a loc
On 26/07/2019 19:36, David Kastrup wrote:
...
I run Patchy when I notice something went to staging. Due to its cost,
I tend to abort it when I discover someone else pushing before me.
So it would appear that your repository (and probably that of Knut) have
a local master branch which would mas
Knut Petersen writes:
> On 27.07.19 07:56, David Kastrup wrote:
>>
>>> What happened to the musicxml2ly patch? It vanished from staging.
>>> Shall I push it again?
>> It didn't pass patchy testing on my computer with failures in the
>> musicxml files. So it appears to have a problem with, uh, Py
