On Tue, Oct 24, 2017 at 10:43 PM, James Almer <jamr...@gmail.com> wrote: > Maybe first ask what the workaround Nicolas mentioned is about?
This was not meant to push anything on anyone. Just wanted to let him know what had been come up with elsewhere. > And preferably don't quote me on this subject. This is not my area of > expertise and i simply gave a suggestion to keep the old behavior at > least for a while, assuming this is an API break. And my suggestion was > in fact the opposite of what everyone else agreed on in the end. Sorry. It's just that I finally got people talking about it, which as you can see by this thread is not something happening as much here. Will not do again. And yes, but you seemed to agree at the end. That might have just been my misunderstanding. And yes, I am not an expert on this either. I just knew about the general breakage and the fact that no actions were yet taken regarding it, so I tried to start a discussion about alternatives of handling this. Jan _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
