Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC PATCH] avformat: remove HLS protocol
Date: Tue, 8 Jul 2025 23:01:16 +0200 (CEST)
Message-ID: <b057a893-d85d-bce0-fbd3-98fcec2f2b6e@passwd.hu> (raw)
In-Reply-To: <7b1e57da-f41-8686-4e35-fe243f867baf@martin.st>



On Tue, 8 Jul 2025, Martin Storsjö wrote:

> On Tue, 8 Jul 2025, Marvin Scholz wrote:
>
>>  The use of this protocol was already discouraged and warned about
>>  for years with the recommendation to use the HLS demuxer instead.
>>  ---
>>  doc/protocols.texi      |  20 ---
>>  libavformat/Makefile    |   2 -
>>  libavformat/hlsproto.c  | 318 ----------------------------------------
>>  libavformat/protocols.c |   1 -
>>  4 files changed, 341 deletions(-)
>>  delete mode 100644 libavformat/hlsproto.c
>
> I'm ok with this removal.
>
> I'll leave it up to others to clarify if it's ok to just remove it outright 
> or if we need to do some even further deprecation around it, etc. (We've had 
> an explicit warning discouraging the use of this since 
> 9cb9c6c42dcd08746e0684eeacccf8b89b12e571 in 2012.)

I think it is fine to simply remove it. Maybe add a changelog entry for 
the removal.

Regards,
Marton
_______________________________________________
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-07-08 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 19:14 Marvin Scholz
2025-07-08 20:59 ` Martin Storsjö
2025-07-08 21:01   ` Marton Balint [this message]

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=b057a893-d85d-bce0-fbd3-98fcec2f2b6e@passwd.hu \
    --to=cus@passwd.hu \
    --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