2017-12-19 0:49 GMT+01:00 Ronald S. Bultje <rsbul...@gmail.com>: > Hi, > > On Mon, Dec 18, 2017 at 6:31 PM, Carl Eugen Hoyos <ceffm...@gmail.com> > wrote: > >> 2017-12-18 14:00 GMT+01:00 Ronald S. Bultje <rsbul...@gmail.com>: >> > Hi, >> > >> > On Mon, Dec 18, 2017 at 12:28 AM, Gyan Doshi wrote: >> > >> >> Hi Ronald, >> >> >> >> When do you expect to apply this? >> >> > Oops, forgot; pushed. >> >> Sorry if my email was really so unclear! >> >> Even by my (low) standards, this patch was horrible and should >> not have been committed, sorry if you disagree and sorry if you >> believe I didn't make this clear in my first email. >> >> Please fix this mess, see #6921. >> >> Thank you, Carl Eugen >> > > Please keep discussions on the list. > > I've mentioned (in my earlier email) that this could indeed use a version > bump in libvmaf. If #6921 is related to this patch, updating libvmaf would > probably be the correct solution both before and after such a version bump.
How is this related to the missing configure check? Carl Eugen _______________________________________________ ffmpeg-devel mailing list email@example.com http://ffmpeg.org/mailman/listinfo/ffmpeg-devel