From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavfi: get rid of FF_INTERNAL_FIELDS
Date: Tue, 31 Jan 2023 15:32:45 +0100
Message-ID: <Y9kmjfcqJYGWDxP4@phare.normalesup.org> (raw)
In-Reply-To: <CAPYw7P5VbHXcCspU2g4BezuEL+Ngn_zTQTwQwW2S234sqoQ7eA@mail.gmail.com>
Paul B Mahol (12023-01-31):
> No, you do not. Calling your libavfilter framework code "complex" is disgrace
> to really complex code in non-framework part of libavfilter or else in
> FFmpeg libraries.
>
> libavfilter framework needs serious overhaul.
> It have numerous limitations and other stuff too much exposed to user,
> that really should not be.
>
> You do not maintain code at all, you just block patches and never
> contribute anymore anything useful besides blocking patches.
… says the person who does not know that the duration between pts=3 and
pts=5 must be 2.
This is a bad joke.
--
Nicolas George
_______________________________________________
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:[~2023-01-31 14:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:29 Anton Khirnov
2023-01-30 12:32 ` Paul B Mahol
2023-01-30 12:40 ` Nicolas George
2023-01-31 13:50 ` Anton Khirnov
2023-01-31 14:03 ` Nicolas George
2023-01-31 14:14 ` Paul B Mahol
2023-01-31 14:32 ` Nicolas George [this message]
2023-01-31 14:50 ` Paul B Mahol
2023-01-31 14:18 ` Anton Khirnov
2023-01-31 14:31 ` Nicolas George
2023-01-31 15:24 ` Anton Khirnov
2023-01-31 16:13 ` Nicolas George
2023-01-31 16:34 ` Nicolas George
2023-01-31 21:02 ` Andreas Rheinhardt
2023-01-31 21:16 ` Nicolas George
2023-02-01 0:31 ` Andreas Rheinhardt
2023-02-01 7:47 ` Nicolas George
2023-02-01 13:48 ` Andreas Rheinhardt
2023-02-03 14:45 ` Nicolas George
2023-02-04 11:09 ` Uoti Urpala
2023-02-04 15:27 ` Andreas Rheinhardt
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=Y9kmjfcqJYGWDxP4@phare.normalesup.org \
--to=george@nsup.org \
--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