Re: Issue 1213 in lilypond: Segmentation fault : extender triggers an infinite loop in Context::now_mom ()

[lilypond]

Updates:
        Labels: Priority-Postponed

Comment #2 on issue 1213 by percival.music.ca: Segmentation fault :  
extender triggers an infinite  loop in Context::now_mom  ()
http://code.google.com/p/lilypond/issues/detail?id=1213

Hmm.  I see why Ralph didn't give it a priority.  :)

Honestly, I'm stumped.  I really don't like doing this, but I think the  
only "honest" solution is to officially reject the bug report and mark it  
invalid.
- nobody is ever going to fix it.
- even if they _did_ fix it, we're not going to make any more 2.12 releases.

It feels really bad, though... that would basically mean that we're  
announcing that we don't officially support *any* version of lilypond.   
(people shouldn't be using 2.13 yet, but we'd be rejecting a real and  
serious bug report about the recommended 2.12)

OTOH, I don't seen any benefit from agonising over this issue for weeks.   
Yes, the original bug reporter would be justified in being pissed, but I  
can't see *any* benefit (other than placating them) to keeping this report  
around.

Hmm... actually, let's just mark it "postponed".  That's our  
default "wontfix" priority.  We can leave it there for a few weeks, then  
once 2.14 is out, we can mark it closed because we can't reproduce it with  
the latest stable.