Issue 2156 in lilypond: lost commits

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Critical

New issue 2156 by address@hidden: lost commits
http://code.google.com/p/lilypond/issues/detail?id=2156

Staging was broken on Dec 23.  That was forked into:
  staging-broken-dec-23
which does NOT compile.

After some testing, a subset of those commits was forked into:
  staging-broken-dec-26
which does NOT compile.

Right now, we have approximately 10 commits which are on  
staging-broken-dec-23, of which probably 9 are good.  Those commits are in  
limbo and can reasonably be considered to be LOST unless somebody rescues  
them.

There are (at least) two tasks here:
1. identify the broken commits.
2. rescue the good commits.
3. fix the broken commits and/or flag those issues as not being fixed.

This is a mess.