[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1612 in lilypond: Change staff produces long stems
From: |
lilypond |
Subject: |
Re: Issue 1612 in lilypond: Change staff produces long stems |
Date: |
Mon, 02 May 2011 13:18:57 +0000 |
Comment #21 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
I'm guessing that my comment 18 about "already pushed his patches" is
referring to some subset (not necessarily a proper subset, though) of:
275ef7f1fdbe054f1c9f6685bddda5c2aa0b47e2
fd38be6ef12fedfc51f15052f6160f91fa456e8f
65aaa693afc29019ebf3d358d00914bed6e8baf5
Hopefully somebody can identify the exact commit(s) which should be
backported.
Of course, his later commits
f9116bac398f94d95e237aa3b1fc222a59ad8e3c
104566603d933821fbdbb7696ef0b5bbd3fa0797
might also be candidates for backporting.
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/02
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/02
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems,
lilypond <=
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/02
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/02
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/03
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/04
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/07
- Message not available
- Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/05/27
Re: Issue 1612 in lilypond: Change staff produces long stems, address@hidden, 2011/05/02