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
On Nov 5, 2013, at 9:23 AM, David Kastrup d...@gnu.org 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
Mike Solomon m...@mikesolomon.org writes:
On Nov 5, 2013, at 9:23 AM, David Kastrup d...@gnu.org 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
David Kastrup d...@gnu.org writes:
Mike Solomon m...@mikesolomon.org writes:
On Nov 5, 2013, at 9:23 AM, David Kastrup d...@gnu.org 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
2013/11/5 David Kastrup d...@gnu.org:
Mike Solomon m...@mikesolomon.org writes:
On Nov 5, 2013, at 9:23 AM, David Kastrup d...@gnu.org 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
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.
karol karo...@wp.pl 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_
