Updates:
Status: Fixed
Labels: -Patch-review Fixed_2_17_30
Comment #9 on issue 3639 by [email protected]: tuplet of a single chord gives a
syntax error
http://code.google.com/p/lilypond/issues/detail?id=3639
I'm quite unenthused of pushing a large change like this without much of a
review period, but it is unlikely anybody but myself will actually _review_
it, so in order to get _testing_ feedback about it in time to have this
regression addressed reliably (if necessary, backing this out again and
designing a different strategy), it needs to appear in developer releases
_now_.
So pushing to staging as
commit 792175df3301a04ba29f3f5b9d2d7f50c318b5e3
Author: David Kastrup <[email protected]>
Date: Thu Oct 31 15:22:07 2013 +0100
Issue 3639/2: allow chords in optional arguments
commit 914ac72ad696b024028c7a9d8936180059d65d27
Author: David Kastrup <[email protected]>
Date: Thu Oct 31 15:22:07 2013 +0100
Issue 3639/1: allow \repeat in optional arguments
commit 2e5054af248270d7109f40a3314f744e0f8c3930
Author: David Kastrup <[email protected]>
Date: Wed Oct 30 13:42:31 2013 +0100
Eliminate closed argument lists before UNSIGNED and durations
commit 575fa1db7291e88f7f888a6b1bcae9ac02d6a093
Author: David Kastrup <[email protected]>
Date: Wed Oct 30 13:03:01 2013 +0100
Remove closed expressions before postevents and negative numbers
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
