Graham Percival <gra...@percival-music.ca> writes:

> I haven't seen any interest in
>   http://code.google.com/p/lilypond/issues/detail?id=1771

My take on this (if nobody is going to protest in the next few hours) is
to revert the flawed fix.

Reason: we get rid of a critical issue.

The original bug fixer does not appear to be in the queue for fixing the
effects of his patch, and the patch adds a considerable amount of
material.

For me this means that it is easier to think about fixing the original
bug than it is thinking about the flawed fix.

I'll revert in my personal copy and start thinking from there.  However,
it will be about noonish before I actually have time.

The other critical bug appears to be related with multithreading, and I
consider it likely, given its random appearance, that it will mainly
affect multicore systems.  I don't have such a one.

-- 
David Kastrup


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to