On Oct 2, 2011, at 3:16 AM, Colin Campbell wrote:

> Here is a list of patches which have had no changes for four weeks or more.  
> I propose to mark them abandoned on Monday, unless their status changes.  If 
> you update your patches, they should be marked New, to trigger the review 
> process.  If you agree that the patch is abandoned, you should probably close 
> your Rietveld item as well.
> 
> Issue 1729: Set spanner length as a spanner property - R 4641085

Nixed it.

> Issue 1435: [PATCH] PartCombine: Keep track of the state in the 
> Part_combine_engraver (issue3334043)
> Issue 1727: Adds glissando stems to lilypond - R 4661061

I'd like to keep this on-line: it should not go on a countdown (it is still 
just a sketch), but it contains a lot of ideas that I may need to pull off 
Rietveld and use in the future.

> Issue 1693: Attaches bound info to beam for better normalized-endpoint 
> calculations - R 4605047

Nixed it.

> Issue 1567: Add documentation for footnotes 
> Issue 1063: Reverting nested property fails to restore default value if 
> preceded by override in same grob
> Issue 1506: \tempo after StopStaff/StartStaff forces extension of staff symbol

As I said previously, I don't mind adopting this guy.

> Issue 1417: regtests "time" field is broken
> Issue 39: collision flag notehead with polyphony
> Issue 706: ledger lines should take simultaneous notes' accidentals into 
> account
> Issue 737: Enhancement: support for footnotes and/or endnotes.

If you could leave this up for another week, that'll give me time to collect 
the bounty on it.

Thanks!
~Mike
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to