Re: Issue 1695 in lilypond: Clef change placed outside score

[lilypond]

Comment #3 on issue 1695 by percival.music.ca: Clef change placed outside  
score
http://code.google.com/p/lilypond/issues/detail?id=1695

the problem occurred between
BAD:
  9a63326816f586dd79d326776583697f95203330
and GOOD:
  d3d40f3469eda2cb327bebbd392c1ce88b114394

but unfortunately the bisect in the middle has a broken commit which  
doesn't compile. :(

there's probably some way to make git test a commit manually (so that I  
could avoid the broken-compile commit), but that range only has about 10  
commits in it, so at least I've reduced the range?