From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] The "bad" Patch
Date: Wed, 28 May 2025 18:09:51 +0000
Message-ID: <DM8P223MB0365BD9EFD253AA9345B541CBA67A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB0365059111079F8788127808BA67A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> softworkz .
> Sent: Mittwoch, 28. Mai 2025 20:01
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] The "bad" Patch
>
>
>
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Rémi
> > Denis-Courmont
> > Sent: Mittwoch, 28. Mai 2025 19:34
> > To: FFmpeg development discussions and patches <ffmpeg-
> > devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] The "bad" Patch
> >
> > Hi,
> >
> > Whatever glibc does or doesn't do is kinda irrelevant. FFmpeg is
> > supposed to be portable and that makes `system()` a non-starter
> given
> > how bad it *can* be.
>
> On Windows it runs ShellExecute, on Mac it does nothing.
> We're talking about Linux only - which was the focus of the comments.
>
>
>
> > With that said, and with my CC hat on, if you would consider a
> > portably safer alternative, I can only say that considering what
> > strong objections there were, and who made them, the only way
> forward
> > (if any) is to solicit the TC.
>
> I don't want this patch to be merged.
>
> And this cannot be wiped away by referring to any general sayings. The
> patch is very specific and when somebody makes drastic comments like
> the
> ones that were made, then I expect that these were made based on
> thorough
> evaluation and consideration.
>
> Now, I'm asking those persons to lay out their considerations at a
> technical level, specific to the code in that patch - or apologize for
> their invalid assessments.
Probably nobody will have the moral courage to apologize, anyway.
Not being able to explain their assessments will suffice.
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".
next prev parent reply other threads:[~2025-05-28 18:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 15:24 softworkz .
2025-05-28 17:34 ` Rémi Denis-Courmont
2025-05-28 18:01 ` softworkz .
2025-05-28 18:09 ` softworkz . [this message]
2025-05-28 18:27 ` Marton Balint
2025-05-28 18:46 ` softworkz .
2025-05-29 2:59 ` softworkz .
2025-05-29 9:55 ` Nicolas George
2025-05-31 11:44 ` softworkz .
2025-05-31 16:21 ` Mark Thompson
2025-05-31 18:28 ` softworkz .
2025-05-31 20:26 ` Mark Thompson
2025-06-02 6:09 ` softworkz .
2025-06-02 7:31 ` softworkz .
2025-05-31 16:59 ` softworkz .
2025-05-31 17:34 ` softworkz .
2025-06-01 23:21 ` Michael Niedermayer
2025-06-01 23:51 ` softworkz .
2025-06-02 7:57 ` Nicolas George
2025-06-02 9:31 ` softworkz .
2025-06-02 10:18 ` softworkz .
2025-06-02 10:49 ` Nicolas George
2025-06-02 19:30 ` softworkz .
2025-06-02 21:26 ` softworkz .
2025-06-02 19:34 ` Michael Niedermayer
2025-06-02 21:22 ` softworkz .
2025-06-03 1:06 ` Michael Niedermayer
2025-06-01 23:56 ` softworkz .
2025-05-31 18:38 ` Kieran Kunhya via ffmpeg-devel
2025-05-29 14:43 ` Nicolas George
2025-05-30 3:42 ` softworkz .
2025-05-31 19:31 ` Leo Izen
2025-05-31 19:34 ` Marvin Scholz
2025-05-31 20:08 ` softworkz .
2025-05-31 20:13 ` 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=DM8P223MB0365BD9EFD253AA9345B541CBA67A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.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