Quoting James Almer (2023-05-09 13:56:22) > On 5/9/2023 7:30 AM, Anton Khirnov wrote: > > There is nothing meaningful the caller can do with it. > > --- > > libavcodec/alsdec.c | 6 +++++- > > libavcodec/apac.c | 6 ++++-- > > libavcodec/apedec.c | 6 +++++- > > libavcodec/atrac3.c | 12 ++++++++++-- > > libavcodec/atrac9dec.c | 6 +++++- > > libavcodec/bonk.c | 6 ++++-- > > libavcodec/codec.h | 3 +++ > > libavcodec/ftr.c | 6 +++++- > > libavcodec/g723_1dec.c | 6 +++++- > > libavcodec/g729dec.c | 12 ++++++++++-- > > libavcodec/libspeexdec.c | 6 +++++- > > libavcodec/misc4.c | 5 ++++- > > libavcodec/shorten.c | 6 ++++-- > > libavcodec/tests/avcodec.c | 3 +-- > > libavcodec/version_major.h | 1 + > > libavcodec/wavarc.c | 2 ++ > > libavcodec/wmalosslessdec.c | 6 +++++- > > libavcodec/wmaprodec.c | 18 +++++++++++++++--- > > libavcodec/wmavoice.c | 6 +++++- > > 19 files changed, 98 insertions(+), 24 deletions(-) > > Missing APIChanges entry. > > For that matter, when there's no replacement for a deprecated API, and > thus there's no point in bumping minor, what should the APIChanges entry > point to?
Is there a point in having an APIchanges entry when no API actually changed? -- Anton Khirnov _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".