Re: incomplete tuplets in non-standard time signatures

[Jonas Hahnfeld]

Am Sonntag, dem 29.11.2020 um 22:24 +0100 schrieb Michael Käppler:
> Am 29.11.2020 um 21:09 schrieb Lukas-Fabian Moser:
> > Hi Harm,
> Hi Harm and Lukas,
> > 
> > > I just filed a bug report
> > > http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html
> > > 
> > 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit
> > commit 2c2908c905ba822ef656b06b1cc4f0ca33960c9c
> > Author: Malte Meyn <lilypond@maltemeyn.de>
> > Date:   Sun Sep 29 10:10:35 2019 +0200
> > 
> >     Issue 5563: make edges of brackets dashable
> > 
> >     The new boolean grob property dashed-edge controls whether the
> > edges of
> >     a dashed bracket are solid or dashed.
> > 
> > 
> That does not make sense to me. 2.20.0 was released on March 1, 2020 and
> Harm reported
> that 2.20.0 is fine. I think bisecting must start with 2.20.0., then.

It does very much make sense: 2.20.0 was not released from master;
instead stable/2.20 was branched in August 2017. All commits since then
until April 2020 first appeared in 2.21.0 (unless backported for 2.20).

Jonas

signature.asc
Description: This is a digitally signed message part