> > The good approach is to fix the bugs. You do not need to fix all of > them, just fix the one or two instances that break things for you: in > your use case, there is one line of code in the whole project that gets > ret=0 and thinks it means EOF: find it and fix it, and you should be > good. Other instance, if any, can be fixed as needed. >
I tried this approach but when I changed that one critical line, 10 other things got broken according to fate. Even if I fixed them and posted patches here in list, I was sugested to thorougouhly test all other protocol modules to make sure it doesn't break anything else but that's not possible (at least I'm not able to). So what other option I have than trying to submit a workaround? -- S pozdravom / Best regards Daniel Kucera. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
