From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] STF RaptorQ
Date: Fri, 23 May 2025 13:33:06 +0200
Message-ID: <20250523113306.GY29660@pb2> (raw)
In-Reply-To: <CABGuwEm-UKk2pq2-rZ6b+fFq+APWRxD0v9O8v8+J7S8sCUQZtQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1228 bytes --]
Hi Kieran
On Fri, May 23, 2025 at 08:51:43AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
[...]
> I appreciate the way the 2024 organisers ran STF was not exactly stellar
It seems every mail you post is an attack on FFmpeg or the FFmpeg Team
And its alot of different people you target. And often people who
have done good and valuable work
Seriously, I could easily talk negatively about you in every mail i
write too but i dont, i try to be polite and positive.
As an example i could have instead replied with a tone matching yours:
(below is a (true) example of communication in the same tone as yours
that i avoid)
"I appreciated the stellar service you provided by providing and
hosting a trac server for FFmpeg. It had only one broken cpu core.
You only once decided to use the FFmpeg server to test some random
audio hardware.
Its sad that our users need reliable service"
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
than the original author, trying to rewrite it will not make it better.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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:[~2025-05-23 11:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 23:42 Kieran Kunhya via ffmpeg-devel
2025-05-22 23:55 ` Devin Heitmueller
2025-05-23 3:48 ` Lynne
2025-05-23 14:37 ` Devin Heitmueller
2025-05-23 9:45 ` Michael Niedermayer
2025-05-23 9:58 ` Michael Niedermayer
2025-05-23 11:25 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 14:57 ` Devin Heitmueller
2025-05-23 15:59 ` Michael Niedermayer
2025-05-23 11:32 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 16:24 ` Tristan Matthews via ffmpeg-devel
2025-05-23 14:50 ` Devin Heitmueller
2025-05-23 15:00 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 15:45 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 20:35 ` Michael Niedermayer
2025-05-23 21:45 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 16:04 ` Michael Niedermayer
2025-05-23 3:44 ` Lynne
2025-05-23 6:50 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 9:53 ` Lynne
2025-05-23 7:51 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 11:33 ` Michael Niedermayer [this message]
2025-05-23 12:13 ` Kieran Kunhya via ffmpeg-devel
2025-05-23 14:43 ` Michael Niedermayer
2025-05-24 16:39 ` [FFmpeg-devel] Previous trac server hosting Was: " Michael Niedermayer
2025-05-24 17:48 ` Kieran Kunhya via ffmpeg-devel
2025-06-02 4:29 ` Baptiste Coudurier
2025-05-23 14:58 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
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=20250523113306.GY29660@pb2 \
--to=michael@niedermayer.cc \
--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