Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add sdlvsink for video display
Date: Fri, 07 Jun 2024 14:54:51 +0300
Message-ID: <05E9959A-9743-4C57-AAEB-186EACE9F161@remlab.net> (raw)
In-Reply-To: <20240607095351.GP2821752@pb2>



Le 7 juin 2024 12:53:51 GMT+03:00, Michael Niedermayer <michael@niedermayer.cc> a écrit :
>We can require anything from an API that we are able to change and extend
>Of course we can decide not to allow such requirment even if optional
>but we surely _could_ add such a feature if we choose to do so

Sure. You can also require infinite memory or an oracle be provided. That's just not going to happen though. And having libraries depend on the main thread is a well-documented malpractice.

I don't think we should add maintenance burden with code that can't be used safely.
_______________________________________________
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".

  parent reply	other threads:[~2024-06-07 11:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 11:51 Shiqi Zhu
2024-06-06 12:20 ` Zhao Zhili
2024-06-07  2:12   ` Hiccup Zhu
2024-06-07  2:32     ` Zhao Zhili
2024-06-07  3:33       ` Shiqi Zhu
2024-06-07  6:45         ` Rémi Denis-Courmont
2024-06-07  9:53           ` Michael Niedermayer
2024-06-07 10:46             ` Anton Khirnov
2024-06-07 11:54             ` Rémi Denis-Courmont [this message]
2024-06-11 13:13               ` Shiqi Zhu
2024-06-12 19:52                 ` Stefano Sabatini
2024-06-12 20:14                   ` Paul B Mahol
2024-06-13  1:49                     ` Shiqi Zhu
2024-06-13  1:54                   ` Shiqi Zhu

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=05E9959A-9743-4C57-AAEB-186EACE9F161@remlab.net \
    --to=remi@remlab.net \
    --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