Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: Re: [FFmpeg-devel] [PATCH 2/5] fftools/ffmpeg: move parsing of -stats_* specifiers to lavu/parseutils
Date: Thu, 14 Dec 2023 19:42:06 +0100
Message-ID: <1f033dae-8727-4573-a91a-767d74c609c8@mail.de> (raw)
In-Reply-To: <170257627944.8914.2969565919416524493@lain.khirnov.net>

Am 14.12.23 um 18:51 schrieb Anton Khirnov:
> Quoting Thilo Borgmann via ffmpeg-devel (2023-12-14 11:34:11)
>> Am 14.12.23 um 06:23 schrieb Anton Khirnov:
>>> Quoting Thilo Borgmann via ffmpeg-devel (2023-12-13 19:17:04)
>>>> Am 13.12.23 um 17:28 schrieb Anton Khirnov:
>>>>> It is bad practice to design library features around the needs and
>>>>> limitations of a single specific caller.
>>>>
>>>> The callers here would be the CLI and this filter.
>>>
>>> First, public APIs should be designed for general classes of use cases,
>>> not specific callers.
>>
>> Parsing a "...{var0}...{varN}..." string for its variables appears quite generic to me.
>> IMO, especially for libavutil, you think a bit too ideological here.
> 
> You're not parsing generic variables though, but a predefined list of
> highly specific ones.
> 
>> A) How about putting it under avpriv_ then?
> 
> 1) fftools are not allowed to use avpriv functions.
> 2) It does not solve any of the problems I pointed out.
> 
>> B) Not filibustering
> 
> https://en.wiktionary.org/wiki/filibuster
> 2. (US politics) A tactic (such as giving long, often irrelevant
>     speeches) employed to delay the proceedings of, or the making of a
>     decision by, a legislative body,
> 
> Are you seriously calling my comments irrelevant stalling?

No, sorry, I just mean endless discussing of this disagreement.

Going to send a fixed format version.

-Thilo
_______________________________________________
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:[~2023-12-14 18:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 15:07 [FFmpeg-devel] [PATCH 0/5] avfilter: Add fsync filter Thilo Borgmann via ffmpeg-devel
2023-12-11 15:07 ` [FFmpeg-devel] [PATCH 1/5] fftools/ffmpeg: split loop for parsing and validation of -stats_* specifiers Thilo Borgmann via ffmpeg-devel
2023-12-11 15:07 ` [FFmpeg-devel] [PATCH 2/5] fftools/ffmpeg: move parsing of -stats_* specifiers to lavu/parseutils Thilo Borgmann via ffmpeg-devel
2023-12-13 12:00   ` Anton Khirnov
2023-12-13 12:05     ` Thilo Borgmann via ffmpeg-devel
2023-12-13 12:08       ` Anton Khirnov
2023-12-13 12:15         ` Thilo Borgmann via ffmpeg-devel
2023-12-13 12:39           ` Anton Khirnov
2023-12-13 12:50             ` Thilo Borgmann via ffmpeg-devel
2023-12-13 16:28               ` Anton Khirnov
2023-12-13 18:17                 ` Thilo Borgmann via ffmpeg-devel
2023-12-14  5:23                   ` Anton Khirnov
2023-12-14 10:34                     ` Thilo Borgmann via ffmpeg-devel
2023-12-14 17:51                       ` Anton Khirnov
2023-12-14 18:42                         ` Thilo Borgmann via ffmpeg-devel [this message]
2023-12-13 12:10   ` Nicolas George
2023-12-11 15:07 ` [FFmpeg-devel] [PATCH 3/5] reindent after last commit Thilo Borgmann via ffmpeg-devel
2023-12-11 15:07 ` [FFmpeg-devel] [PATCH 4/5] avfilter: Add fsync filter Thilo Borgmann via ffmpeg-devel
2023-12-11 15:14   ` Thilo Borgmann via ffmpeg-devel
2023-12-11 15:07 ` [FFmpeg-devel] [PATCH 5/5] fate: Add fsync filter tests Thilo Borgmann via ffmpeg-devel

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=1f033dae-8727-4573-a91a-767d74c609c8@mail.de \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=thilo.borgmann@mail.de \
    /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