From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/3] lavc: deprecate AV_CODEC_CAP_SUBFRAMES
Date: Tue, 9 May 2023 08:56:22 -0300
Message-ID: <51a6fb30-cfed-cfbb-6dc7-96c3a1f7a55a@gmail.com> (raw)
In-Reply-To: <20230509103041.5537-2-anton@khirnov.net>
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?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-05-09 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 10:30 [FFmpeg-devel] [PATCH 1/3] lavc/decode: drop a useless warning Anton Khirnov
2023-05-09 10:30 ` [FFmpeg-devel] [PATCH 2/3] lavc: deprecate AV_CODEC_CAP_SUBFRAMES Anton Khirnov
2023-05-09 11:56 ` James Almer [this message]
2023-05-09 12:02 ` Anton Khirnov
2023-05-09 12:40 ` James Almer
2023-05-09 13:57 ` [FFmpeg-devel] [PATCH v2 " Anton Khirnov
2023-05-09 10:30 ` [FFmpeg-devel] [PATCH 3/3] fftools/opt_common: stop printing deprecated AV_CODEC_CAP_SUBFRAMES Anton Khirnov
2023-05-09 10:51 ` [FFmpeg-devel] [PATCH 1/3] lavc/decode: drop a useless warning Paul B Mahol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51a6fb30-cfed-cfbb-6dc7-96c3a1f7a55a@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git