[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn
From: |
lilypond |
Subject: |
Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff |
Date: |
Sun, 18 Jul 2010 16:31:34 +0000 |
Updates:
Owner: ---
Labels: Bounty
Comment #4 on issue 442 by v.villenave: Enhancement:
RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff
http://code.google.com/p/lilypond/issues/detail?id=442
According to Graham, it should only take an experienced dev. a few hours to
address this issue. I'm not sure a €50 bounty could help here, but let's
give it a try anyway...
Jan, Neil, anyone? 50 bucks waiting for you here :-)
- Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff,
lilypond <=
- Message not available
- Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff, lilypond, 2010/07/22
- Message not available
- Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff, lilypond, 2010/07/22
- Message not available
- Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff, lilypond, 2010/07/23
- Message not available
- Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff, lilypond, 2010/07/23
- Message not available
- Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff, lilypond, 2010/07/23
- Message not available
- Re: Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff, lilypond, 2010/07/23