[FFmpeg-devel] [PATCH 2/3] lavc: replace ff_thread_get_buffer() with ff_get_buffer()

[Sean McGovern]

On Fri, Mar 8, 2024, 10:37 Vittorio Giovara <vittorio.giovara at gmail.com>
wrote:

> On Fri, Mar 8, 2024 at 4:34 PM Sean McGovern <gseanmcg at gmail.com> wrote:
>
> > On Fri, Mar 8, 2024, 10:31 Paul B Mahol <onemda at gmail.com> wrote:
> >
> > > On Fri, Mar 8, 2024 at 4:21 PM Vittorio Giovara <
> > > vittorio.giovara at gmail.com>
> > > wrote:
> > >
> > > > On Fri, Mar 8, 2024 at 4:10 PM Sean McGovern <gseanmcg at gmail.com>
> > wrote:
> > > >
> > > > > On Fri, Mar 8, 2024, 08:20 Nicolas George <george at nsup.org> wrote:
> > > > >
> > > > > > Andreas Rheinhardt (12024-03-08):
> > > > > > > What maintenance cost and complexity are you referring to? I
> > > checked
> > > > > and
> > > > > > > could not find a single commit where one had to fix an
> > > > ff_get_buffer()
> > > > > > > to ff_thread_get_buffer() because it has been forgotten when
> the
> > > > > decoder
> > > > > > > has been declared to support frame threading.
> > > > > >
> > > > > > Welcome to the new FFmpeg, where absolute consistency, i.e.
> > catering
> > > > for
> > > > > > hypothetical mediocre contributors, is more important than easy
> > > > > > optimizations and new approaches.
> > > > > >
> > > > > > And if you do not like it, “shut up, I'm on the TC and I won't
> > > recuse”.
> > > > > >
> > > > > > And if you do not like that, “shut up, I'm on the CC too”.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > --
> > > > > >   Nicolas George
> > > > > > _______________________________________________
> > > > > > ffmpeg-devel mailing list
> > > > > > ffmpeg-devel at ffmpeg.org
> > > > > > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> > > > > >
> > > > > > To unsubscribe, visit link above, or email
> > > > > > ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
> > > > > >
> > > > >
> > > > > Everybody can we *please* keep the responses civil/professional on
> > the
> > > > ML.
> > > > >
> > > >
> > > > I'd just be happy with "on-topic" but it seems like people with
> agendas
> > > > like to project on unrelated threads.
> > > >
> > >
> > > LibAV actions speak more than words once again.
> > >
> > >
> > > > --
> > > > Vittorio
> > > > _______________________________________________
> > > > ffmpeg-devel mailing list
> > > > ffmpeg-devel at ffmpeg.org
> > > > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> > > >
> > > > To unsubscribe, visit link above, or email
> > > > ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
> > > >
> > > _______________________________________________
> > > ffmpeg-devel mailing list
> > > ffmpeg-devel at ffmpeg.org
> > > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> > >
> > > To unsubscribe, visit link above, or email
> > > ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
> > >
> >
> > It is really mean-spirited to make such comments about a project that is
> no
> > longer in operation. Can't we look forward instead of behind us?
> >
>
> Could you guys look forward in a separate thread? 🙏
> --
> Vittorio
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>

I see what you did there (ref: $subj)! :)

-- Sean McGovern