* Durk Talsma -- Thursday 25 October 2007: > Probably the best course of action is to send a friendly reminder > to the plib list, and if it doesn't happen again, stick to plan B.
Yes, but I won't do that. I did it on 2007/04/02, and the question remained unanswered. The last posting before that was two and a half months earlier, and the next was two months later. There are nicer places to be ignored. I'm a bit impatient with plib, and I think that integrating the code into fgfs becomes more and more desirable. Which is also a reason why I would like to have the fgfs code cleaned up w.r.t. to the GUI parts. But I can commit my one year old patch right after the release, too. It would just be a pity if people continued to use the broken plib version out of laziness (and because we don't force them to use the fixed one. :-) m. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
