Hello,
Here is the current patch countdown list. The next countdown will be on
December 2nd.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Countdown
Push:
No patches to push at this time.
Dan,
This is a great explanation.
Can you add this to the CG? Anywhere that it seems to make sense.
Thanks,
Carl
On 11/29/19, 3:18 PM, "lilypond-devel on behalf of Dan Eble"
wrote:
On Nov 29, 2019, at 16:20,
wrote:
>
> I am familiar with the use of makefile. So if you
On Nov 29, 2019, at 16:20,
wrote:
>
> I am familiar with the use of makefile. So if you can give me directions with
> some placeholder commands, or comment at the right place in the makefile (s)
Well, start at the "test" target in the top-level GNUmakefile.in. It runs make
in a number of
From: Dan Eble
Sent: Friday, November 29, 2019 4:51 PM
To: lilyp...@de-wolff.org
Cc: lilypond-devel
Subject: Re: create code tests
On Nov 28, 2019, at 19:22, Dan Eble mailto:d...@faithful.be>
> wrote:
Well, step one is to avoid intertwining the existing xml->ly test
infrastructure
On Nov 28, 2019, at 19:22, Dan Eble wrote:
>
> Well, step one is to avoid intertwining the existing xml->ly test
> infrastructure with the new ly->xml test infrastructure. I would put ly->xml
> test input in a different directory. I would probably also plan to rename
>
Han-Wen Nienhuys writes:
> On Tue, Nov 26, 2019 at 8:51 PM David Kastrup wrote:
>> > What level of respect should I maintain for the integrity of
>> > flower/include/yaffut.h? I think it would be nice to limit the
>> > default output of the unit test program to errors + summary, and I
>> >
On Tue, Nov 26, 2019 at 8:51 PM David Kastrup wrote:
> > What level of respect should I maintain for the integrity of
> > flower/include/yaffut.h? I think it would be nice to limit the
> > default output of the unit test program to errors + summary, and I
> > could achieve that either by
