karol writes:
> Not sure if I understand correctly. Does that mean that \override
> MetronomeMark.flag-style will be disabled in stable 2.18?
It will not be available under 2.18, yes. If you want to use this
feature that was created/committed/tested after the line for the
_stable_ 2.18 release
Not sure if I understand correctly. Does that mean that \override
MetronomeMark.flag-style will be disabled in stable 2.18?
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Continuing-towards-2-18-tp153400p153410.html
Sent from the Dev mailing list archive at Nabble.com.
2013/11/5 David Kastrup :
> Mike Solomon writes:
>
>> On Nov 5, 2013, at 9:23 AM, David Kastrup wrote:
>>
>>> So I'm
>>> more comfortable reverting it as well.
>>>
>>
>> Go for it, but could someone please remind me to push it to 2.19 if I
>> forget?
>
> Oh, I was not suggesting to revert anythi
David Kastrup writes:
> Mike Solomon writes:
>
>> On Nov 5, 2013, at 9:23 AM, David Kastrup wrote:
>>
>>> So I'm
>>> more comfortable reverting it as well.
>>>
>>
>> Go for it, but could someone please remind me to push it to 2.19 if I
>> forget?
>
> Oh, I was not suggesting to revert anythin
Mike Solomon writes:
> On Nov 5, 2013, at 9:23 AM, David Kastrup wrote:
>
>> So I'm
>> more comfortable reverting it as well.
>>
>
> Go for it, but could someone please remind me to push it to 2.19 if I
> forget?
Oh, I was not suggesting to revert anything in master. So this and
Thomas' comm
On Nov 5, 2013, at 9:23 AM, David Kastrup wrote:
> So I'm
> more comfortable reverting it as well.
>
Go for it, but could someone please remind me to push it to 2.19 if I forget?
Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
h
Hi,
after we got 2.17.95 out the door with some minor lacerations, I had a
double take and, well, I got a few things confused.
Here is our current situation:
a stable/2.18 branch has been tied off. Afterwards, several other
changes were committed to master and 2.17.95 was released from master.
