On Wed, Mar 23, 2016 at 4:21 AM, wm4 <nfx...@googlemail.com> wrote: > On Tue, 22 Mar 2016 23:43:26 -0400 > Vittorio Giovara <vittorio.giov...@gmail.com> wrote: > >> On Tue, Mar 22, 2016 at 11:33 PM, Vittorio Giovara >> <vittorio.giov...@gmail.com> wrote: >> > On Tue, Mar 22, 2016 at 2:09 PM, wm4 <nfx...@googlemail.com> wrote: >> >> And replace some doxygen references to them. >> >> >> >> This is as suggested on the mailing list. >> >> --- >> >> libavcodec/avcodec.h | 12 +++++++++--- >> >> libavformat/avformat.h | 4 ++-- >> >> 2 files changed, 11 insertions(+), 5 deletions(-) >> > >> > ok, but don't forget the routine version bump and APIchange entry >> >> and the FF_API guards to the old code > > Such guards don't make sense, because nothing would work if they were > enabled. Disabling deprecation warnings might make sense though.
they make sense if there are compatibility wrappers, which I think we should provide > I'm also wondering where to put user documentation about switching from > old to new API? (Some of that is in the doxygen of the first patch.) Usually that kind of thing goes to the wiki, wiki.libav.org/Migration/12 -- Vittorio _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
