On 7/21/17, Reimar Doeffinger <reimar.doeffin...@gmx.de> wrote:
> On 21.07.2017, at 08:48, Paul B Mahol <one...@gmail.com> wrote:
>
>> On 7/20/17, Carl Eugen Hoyos <ceffm...@gmail.com> wrote:
>>> 2017-07-20 17:46 GMT+02:00 Vittorio Giovara <vittorio.giov...@gmail.com>:
>>>
>>>> + [AV_PIX_FMT_YUV444F32LE] = { 0, 0 },
>>>> + [AV_PIX_FMT_YUV444F32BE] = { 0, 0 },
>>>> + [AV_PIX_FMT_YUVA444F32LE] = { 0, 0 },
>>>> + [AV_PIX_FMT_YUVA444F32BE] = { 0, 0 },
>>>
>>> Feel free to ignore but imo adding (non-hw) pix_fmts that can neither
>>> be read nor written by default FFmpeg is not ok.
>>
>> We will just ignore you as usual.
>
> I don't know what is going on here, but I kind of expected for this kind of
> inappropriate behaviour to finally have died down.
> Stop it, this mailing list is not the place to parade conflicts like a
> trophy, and I believe I am not the only one who simply doesn't want to have
> to read this kind of thing any longer.
Sorry, but this is not mplayer land.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
