[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the s
From: |
lilypond |
Subject: |
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning |
Date: |
Wed, 15 Feb 2012 21:48:23 +0000 |
Updates:
Status: Fixed
Labels: -Patch-review Fixed_2_15_31
Comment #27 on issue 1967 by address@hidden: Concurrent slurs that start and
end at the same moment should not produce a warning
http://code.google.com/p/lilypond/issues/detail?id=1967
After another test (no idea where the midi flake in between came from) and
avoiding an unnecessary conversion, I decided to push as
b986b38f14195f31e26b0a929c8ac23a8ecfc204 to staging.
If this should be copied over to phrasing slurs, anybody up for it?
Version number assigned on the assumption that 2.15.30 is already forked
off.
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, (continued)
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning,
lilypond <=
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, David Kastrup, 2012/02/16
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/18
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, Reinhold Kainhofer, 2012/02/15
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, David Kastrup, 2012/02/15
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, Reinhold Kainhofer, 2012/02/15
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, Reinhold Kainhofer, 2012/02/15