Re: [Lilypond-auto] Issue 4093 in lilypond: put NullVoice in Staff by default

[lilypond]

Comment #3 on issue 4093 by address@hidden: put NullVoice in Staff by default
https://code.google.com/p/lilypond/issues/detail?id=4093

I have no idea why a month-old patch has been resubmitted as a new issue,  
but can we please take the regtest suite breaking down as a sign that my  
repeated statements in that patch review that messing up static grob  
internals in the middle of a context definition is a really bad idea?

Even if subsequent patch amendments will be able to paper over the load of  
rather scary problems now seeping out in the tests, there is a reason for  
the scope of those problems.  This is messing with stuff that has not been  
designed for being messed with.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings