On Sun, 13 Nov 2016 23:50:03 +0100 Carl Eugen Hoyos <ceffm...@gmail.com> wrote:
> 2016-11-11 12:15 GMT+01:00 wm4 <nfx...@googlemail.com>: > > On Fri, 11 Nov 2016 10:19:08 +0100 > > Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > > > >> 2016-11-11 9:03 GMT+01:00 Hendrik Leppkes <h.lepp...@gmail.com>: > >> > On Fri, Nov 11, 2016 at 6:34 AM, Yogender Gupta <ygu...@nvidia.com> > >> > wrote: > > >> >> The included patch should fix. > >> >> > >> > > >> > ffmpeg.c is in the middle of some changes being merged, and once that > >> > is done ffmpeg_cuvid.c will need to be adapted to a new system. Until > >> > then, it would make everything easier if the code actively being > >> > modified by these merges is not modified by hackish fixes. > >> > >> Iirc, the documentation requires to only commit patches that do not > >> (knowingly) break functionality and imo, this implies that you should > >> quickly fix such bugs once they are reported. Or do I miss something? > > > > These are merges. Unless you volunteer to do the merges yourself (and > > properly please) you'll have to live with this. > > Not sure I understand: > Do you mean merges are exempt from any rules and may randomly > break features or introduce bugs? Yes. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
