From: Nicolas George <george@nsup.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/8] lavu: new AVWriter API Date: Tue, 2 May 2023 20:36:53 +0200 Message-ID: <ZFFYRVOWNy4nHArZ@phare.normalesup.org> (raw) In-Reply-To: <2651731.DzIsRRP5fV@basile.remlab.net> [-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --] Rémi Denis-Courmont (12023-05-02): > Please re-read the comments. You are totally misses the point. I confess so, indeed, I completely failed to understand your point after reading your comment multiple times. > Well, I'll add myself to the already long list of people publicly objecting to > your patchset then. I will read your technical comments then. > > There is nothing about heap allocation in this code. And if code can be > > in the framework common to all backends, then it is where it belongs, > > not duplicated in each backend. > This makes zero sense. Why the hell would you want to have more than one heap- > allocation backend. FFmpeg only provides one. Applications can decide to provide their own if they want. That is the point. > Well duh, I wrote the VLC equivalent years ago. And glibc or FreeBSD libc did > them more than a decade before I did. Pointer? > And I decided to object to that on the basis that it's dumb and confusing. The only thing dumb and confusing I see here is the mail I am answering to. > I think I was pretty damn clear and you are just deliberately making up reason > to ignore other people's comments (not just mine). Think what you will about me. -- Nicolas George [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-05-02 18:37 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 9:55 [FFmpeg-devel] [PATCH 1/8] lavu: add macros to help making future-proof structures Nicolas George 2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 2/8] lavu: new AVWriter API Nicolas George 2023-04-28 10:37 ` Rodney Baker 2023-04-28 11:20 ` Nicolas George 2023-05-02 15:53 ` Rémi Denis-Courmont 2023-05-02 16:53 ` Nicolas George 2023-05-02 18:29 ` Rémi Denis-Courmont 2023-05-02 18:36 ` Nicolas George [this message] 2023-05-02 18:46 ` Rémi Denis-Courmont 2023-05-02 18:47 ` Nicolas George 2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 3/8] lavu/writer: add test Nicolas George 2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 4/8] lavf/dump: use a writer Nicolas George 2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 5/8] lavu: add a JSON writer API (WIP) Nicolas George 2023-04-29 9:11 ` Nicolas George 2023-04-29 9:41 ` Anton Khirnov 2023-04-29 14:06 ` James Almer 2023-04-29 17:17 ` Nicolas George 2023-04-29 15:06 ` Derek Buitenhuis 2023-04-30 0:29 ` Kieran Kunhya 2023-05-01 6:20 ` Vittorio Giovara 2023-04-29 17:11 ` Nicolas George 2023-04-29 18:27 ` Anton Khirnov 2023-04-29 18:33 ` Nicolas George 2023-05-01 6:57 ` Leo Izen 2023-05-01 9:51 ` Nicolas George 2023-05-01 10:18 ` Jean-Baptiste Kempf 2023-04-30 15:06 ` Michael Niedermayer 2023-04-30 21:51 ` Kieran Kunhya 2023-05-01 9:46 ` Nicolas George 2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 6/8] lavu: add JSON writer test (WIP) Nicolas George 2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 7/8] lavf/options: add av_disposition_write() Nicolas George 2023-04-28 9:55 ` [FFmpeg-devel] [PATCH 8/8] lavf/dump: use av_disposition_write() Nicolas George 2023-04-29 8:17 ` [FFmpeg-devel] [PATCH 1/8] lavu: add macros to help making future-proof structures Anton Khirnov 2023-04-29 15:11 ` Derek Buitenhuis 2023-05-02 15:36 ` Rémi Denis-Courmont 2023-05-02 16:42 ` Nicolas George 2023-05-02 18:31 ` Rémi Denis-Courmont 2023-05-02 18:38 ` 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=ZFFYRVOWNy4nHArZ@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