From: Devlist Archive <devlist@rlb.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up Date: Tue, 3 Jun 2025 10:15:35 -0700 Message-ID: <CANJxsBkDNT=6NV8uSVbHHb+9Vj762F8uSzXNv4e-ypWaQkY9Ew@mail.gmail.com> (raw) In-Reply-To: <DM8P223MB0365F992AF73ECC728F07A94BA6DA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> > Given the preceding conversations, it is pretty safe to assume > that these comments are based on personal sentiments rather than > technical expertise. While there may be truth to that, it isn't helpful to discount objections without a chance to substantiate them. If the person objecting chooses to not participate in the conversation then the objection cannot be properly accommodated. Any objection that can or should derail progress on a patchset should be addressed if it has substance that will affect the codebase. On Tue, Jun 3, 2025 at 10:07 AM softworkz . < softworkz-at-hotmail.com@ffmpeg.org> wrote: > > > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > Nicolas > > George > > Sent: Dienstag, 3. Juni 2025 18:44 > > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up > > > > Lynne (HE12025-06-04): > > > You don't get to say "oh, there were no more objections, so it was > fine" or > > > "the use is evident" after the mess that your original patchsets were. > > > > > > You're still not using the native time fields, nor the packet buffers, > which > > > is a very hard NAK from me. > > > > Indeed. And not just that. The whole series had many deep logic flaws > > that made it a dead end without a complete rewrite. I explained at the > > time, and “softworkz” was almost as rude then than they are now. My > > patience if more than exhausted, I will not explain again. > > > > Regards, > > > > -- > > Nicolas George > > _______________________________________________ > > > > Given the preceding conversations, it is pretty safe to assume > that these comments are based on personal sentiments rather than > technical expertise. > > > Reference: > > https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2025-June/thread.html > (entire thread) > > sw > _______________________________________________ > 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". > _______________________________________________ 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:[~2025-06-03 17:16 UTC|newest] Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-03 14:20 softworkz . 2025-06-03 16:00 ` Lynne 2025-06-03 16:02 ` James Almer 2025-06-03 16:40 ` Nicolas George 2025-06-03 16:48 ` James Almer 2025-06-03 16:51 ` Devlist Archive 2025-06-03 17:59 ` Nicolas George 2025-06-03 16:12 ` softworkz . 2025-06-03 16:12 ` Devin Heitmueller 2025-06-03 16:43 ` Nicolas George 2025-06-03 17:07 ` softworkz . 2025-06-03 17:15 ` Devlist Archive [this message] 2025-06-03 17:16 ` Devlist Archive 2025-06-03 17:19 ` softworkz . 2025-06-04 15:49 ` Rémi Denis-Courmont 2025-06-04 17:13 ` softworkz . 2025-06-04 17:25 ` Nicolas George 2025-06-04 17:31 ` softworkz . 2025-06-04 19:02 ` softworkz . 2025-06-03 17:17 ` softworkz . 2025-06-03 16:28 ` softworkz . 2025-06-03 18:02 ` Hendrik Leppkes 2025-06-03 18:34 ` Zach Swena 2025-06-04 0:01 ` Michael Niedermayer 2025-06-04 7:13 ` Nicolas George 2025-06-04 7:22 ` Diederick C. Niehorster 2025-06-04 7:25 ` Nicolas George 2025-06-04 17:24 ` softworkz . 2025-06-04 17:29 ` Nicolas George 2025-06-04 17:33 ` softworkz . 2025-06-04 17:35 ` Nicolas George 2025-06-04 17:40 ` softworkz . 2025-06-04 17:44 ` Nicolas George 2025-06-04 17:54 ` softworkz . 2025-06-04 17:57 ` Nicolas George 2025-06-04 18:11 ` softworkz . 2025-06-04 18:12 ` Nicolas George 2025-06-04 18:17 ` softworkz . 2025-06-04 20:42 ` Michael Niedermayer 2025-06-05 0:17 ` softworkz . 2025-06-06 14:32 ` Nicolas George 2025-06-06 14:50 ` Devin Heitmueller 2025-06-08 13:10 ` Nicolas George 2025-06-06 16:54 ` softworkz . 2025-06-07 16:19 ` softworkz . 2025-06-07 17:25 ` Kieran Kunhya via ffmpeg-devel 2025-06-07 17:45 ` softworkz . 2025-06-03 19:13 ` softworkz . 2025-06-04 7:34 ` Nicolas George 2025-06-04 1:16 ` softworkz . 2025-06-04 7:36 ` Nicolas George 2025-06-03 19:23 ` softworkz . 2025-06-04 7:33 ` Nicolas George 2025-06-04 18:35 ` softworkz . 2025-06-05 0:44 ` softworkz .
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='CANJxsBkDNT=6NV8uSVbHHb+9Vj762F8uSzXNv4e-ypWaQkY9Ew@mail.gmail.com' \ --to=devlist@rlb.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