LGTM
http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely#newcode1098
Documentation/notation/spacing.itely:1098: If this block:
How a
Reviewers: dak,
http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely#newcode1182
Documentation/notation/spacing.itely:1182: to struct
http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
http://codereview.appspot.com/6354085/diff/1/Documentation/notation/spacing.itely#newcode1182
Documentation/notation/spacing.itely:1182: to structure the layout
de
"Trevor Daniels" writes:
> David, you wrote Saturday, July 07, 2012 5:13 AM
>
>
>> "Trevor Daniels" writes:
>>
>>> Although I should have noticed the error when git cl asked me to
>>> confirm the issue number, why did it pick the wrong one initially?
>>> How does it make its initial guess?
>>
Trevor Daniels wrote Friday, July 06, 2012 11:18 AM
>
> I'll tart it up a bit and add it to the LSR shortly.
Added to LSR as "Creating a short ossia section with lyrics"
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.o
David, you wrote Saturday, July 07, 2012 5:13 AM
> "Trevor Daniels" writes:
>
>> Although I should have noticed the error when git cl asked me to
>> confirm the issue number, why did it pick the wrong one initially?
>> How does it make its initial guess?
>
> Simple enough. It looks for the f
