From: Marvin Scholz via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Marvin Scholz <code@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] [8.0] avformat/hlsproto: explicitly deprecate it (PR #20311) Date: Fri, 22 Aug 2025 01:29:21 +0300 (EEST) Message-ID: <20250821222921.4B6006800F9@ffbox0-bg.ffmpeg.org> (raw) PR #20311 opened by Marvin Scholz (ePirat) URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20311 Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20311.patch This makes it more clear that it will be removed in a future release. From a6c578ef6555fdb0af0789f8fc673f9188f4b0ec Mon Sep 17 00:00:00 2001 From: Marvin Scholz <epirat07@gmail.com> Date: Fri, 22 Aug 2025 00:28:33 +0200 Subject: [PATCH] avformat/hlsproto: explicitly deprecate it This makes it more clear that it will be removed in a future release. --- libavformat/hlsproto.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/libavformat/hlsproto.c b/libavformat/hlsproto.c index 02f695c1db..1c63a191cb 100644 --- a/libavformat/hlsproto.c +++ b/libavformat/hlsproto.c @@ -206,10 +206,10 @@ static int hls_open(URLContext *h, const char *uri, int flags) goto fail; } av_log(h, AV_LOG_WARNING, - "Using the hls protocol is discouraged, please try using the " - "hls demuxer instead. The hls demuxer should be more complete " - "and work as well as the protocol implementation. (If not, " - "please report it.) To use the demuxer, simply use %s as url.\n", + "Using the hls protocol is deprecated and it will be remove in " + "a future release, please use the hls demuxer instead. " + "If encountering issues with it, please report them. " + "To use the demuxer, simply use %s as url.\n", s->playlisturl); if ((ret = parse_playlist(h, s->playlisturl)) < 0) -- 2.49.1 _______________________________________________ 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".
reply other threads:[~2025-08-21 22:29 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250821222921.4B6006800F9@ffbox0-bg.ffmpeg.org \ --to=ffmpeg-devel@ffmpeg.org \ --cc=code@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