From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavu: header and documentation for AVWriter
Date: Fri, 02 Sep 2022 08:41:28 +0200
Message-ID: <166210088816.3205.3472145427658215743@lain.khirnov.net> (raw)
In-Reply-To: <20220824151828.24218-1-george@nsup.org>
As I already said to you in private, I do not think the motivation and
use cases for this have been sufficiently established.
You claim this will bring massive advantages all over the place. You
should support these claims with some actual patches that demonstrate
these advantages on some real code.
--
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-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-09-02 6:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 15:18 Nicolas George
2022-08-24 15:45 ` Soft Works
2022-08-24 15:59 ` Andreas Rheinhardt
2022-08-24 16:01 ` Nicolas George
2022-08-30 17:08 ` Nicolas George
2022-08-30 19:33 ` Leo Izen
2022-08-30 19:37 ` Nicolas George
2022-08-31 3:13 ` Leo Izen
2022-08-31 3:23 ` Andreas Rheinhardt
2022-08-31 19:28 ` Nicolas George
2022-08-31 23:03 ` Stefano Sabatini
2022-09-01 13:01 ` Nicolas George
2022-09-01 21:33 ` Stefano Sabatini
2022-09-02 6:41 ` Anton Khirnov [this message]
2022-09-07 13:30 ` Nicolas George
2022-09-07 20:05 ` Jean-Baptiste Kempf
2022-09-07 21:13 ` Nicolas George
2022-09-08 16:18 ` Anton Khirnov
2022-09-14 21:29 ` Michael Niedermayer
2023-04-25 17:11 ` Nicolas George
2023-04-25 17:20 ` James Almer
2023-04-28 10:00 ` Nicolas George
2023-04-26 9:05 ` Anton Khirnov
2023-04-28 9:58 ` Nicolas George
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=166210088816.3205.3472145427658215743@lain.khirnov.net \
--to=anton@khirnov.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