From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Captions SCC
Date: Fri, 7 Feb 2025 09:11:56 +0000
Message-ID: <DM8P223MB0365E5FF57B8228D6FEA5C8ABAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <EA9BC91E-8B23-4470-8585-7F04C2D6DC0C@gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Jack Lau
> Sent: Friday, February 7, 2025 9:26 AM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Captions SCC
>
>
> >
> > Hi Jack,
> >
> > "paying attention next time"? That's not the right answer.
> >
> > Please make sure that there won't be a next time.
> >
> > The big evil with LLVMs is not the fact they are making mistakes
> but the extreme level of confidence at which they are presenting
> these mistakes - like no human would do.
> > That's why we tend to fall so easily into taking their trash for
> granted.
> >
> > sw
> >
> >
>
> Hi softworkz,
>
> Thanks for your reply and reminder, I’ll ensure there won't be a next
> time.
>
> Jack
Hi Jack,
thanks for your reply and understanding. I wanted to note that it's not about wrong answers in general.
An answer from yourself that starts with "I think" or similar is very welcome, even when it might be wrong. :-)
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-02-07 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 10:19 Devlist Archive
2025-02-06 12:57 ` Jack Lau
2025-02-07 5:12 ` Devlist Archive
2025-02-07 7:48 ` Soft Works
2025-02-07 7:58 ` Jack Lau
2025-02-07 8:16 ` Soft Works
2025-02-07 8:26 ` Jack Lau
2025-02-07 9:11 ` Soft Works [this message]
2025-02-07 9:44 ` Jack Lau
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=DM8P223MB0365E5FF57B8228D6FEA5C8ABAF12@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