[FFmpeg-devel] [PATCH] avcodec: remove old vdpau decoder implementation

[wm4]

On Sun, 4 Oct 2015 09:25:23 -0400
compn <tempn at mi.rr.com> wrote:

> On Sun, 4 Oct 2015 14:48:25 +0200
> wm4 <nfxjfg at googlemail.com> wrote:
> 
> > On Sun, 4 Oct 2015 11:31:31 +0000 (UTC)
> > Carl Eugen Hoyos <cehoyos at ag.or.at> wrote:
> > 
> > > wm4 <nfxjfg <at> googlemail.com> writes:
> > > 
> > > > On Sat, 3 Oct 2015 22:23:21 +0200
> > > > Carl Eugen Hoyos <cehoyos <at> ag.or.at> wrote:
> > > > 
> > > > > On Saturday 03 October 2015 10:05:29 pm wm4 wrote:
> > > > > > Ping. Will push in 24 hours or so if nobody complains.
> > > > > 
> > > > > The reason I am against this is just that users told me 
> > > > > repeatedly (in person) that they switched from the dark 
> > > > > side to FFmpeg because this (and possibly) other API 
> > > > > was removed there.
> > > > 
> > > > As I've said several times, progress is not possible (or 
> > > > requires lots of wasted energy) if we don't drop obsolete 
> > > > APIs.
> > > 
> > > What makes the old API "obsolete"? You?
> > 
> > Existence of a better API that does everything the old API did. How is
> > this so hard to understand?
> 
> i think carl is asking whom did the deprecating in ffmpeg.
> 
> carl: if this new api works with kodi and mplayer, whats the problem?
> 
> are there still users of this api in 2015? yes or no?
> 
> carl, do you use this api? what for? to test vdpau?
> 
> carl is maintainer of this vdpau code, wm4.
> its right there in MAINTAINERS.
> 
> http://ffmpeg.org/developer.html#Contributing
> 1.4 Development Policy
> 
> 7. Do not commit changes to the build system (Makefiles, configure
> script) which change behavior, defaults etc, without asking first. The
> same applies to compiler warning fixes, trivial looking fixes and to
> code maintained by other developers. We usually have a reason for doing
> things the way we do. Send your changes as patches to the ffmpeg-devel
> mailing list, and if the code maintainers say OK, you may commit. This
> does not apply to files you wrote and/or maintain.
> 
> specifically says do not change code without maintainers approval,
> twice.
> 
> feel free to change developer policy by rfc'ing a patch....
> 
> i'm just trying to help.

Looks like Great Leader violated the developer policy multiple times
then.