From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] FFmpeg table at NAB
Date: Wed, 17 Apr 2024 14:49:50 +0100
Message-ID: <38bff159-d1d3-40cd-954d-9892b78c0077@gmail.com> (raw)
In-Reply-To: <CAHGibzEMGFLqzid6sXi6n+MBmJe5f5D_sYOyQh8Fj+L7Uzxo7w@mail.gmail.com>
On 4/17/2024 12:21 AM, Devin Heitmueller wrote:
> Hello all,
[...]
Yeah, this is exactly what I was screaming into the void about
for literal months, no literally 0 response.
Look for the thread: [FFmpeg-devel] FFmpeg at NAB 2024
It spans months.
My last mail is particularily relevant to your experience:
https://ffmpeg.org//pipermail/ffmpeg-devel/2024-March/324816.html
I assume Thilo was hung over, and thus not on the booth.
It is a disgrace.
- Derek
_______________________________________________
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:[~2024-04-17 13:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 23:21 Devin Heitmueller
2024-04-17 8:03 ` Paul B Mahol
2024-04-17 13:49 ` Derek Buitenhuis [this message]
2024-04-17 13:54 ` James Almer
2024-04-17 13:55 ` Derek Buitenhuis
2024-04-17 19:00 ` [FFmpeg-devel] Mailinglist conduct (was: FFmpeg table at NAB) Ronald S. Bultje
2024-04-17 19:30 ` [FFmpeg-devel] Mailinglist conduct Derek Buitenhuis
2024-04-17 19:33 ` James Almer
2024-04-17 19:43 ` Derek Buitenhuis
2024-04-17 20:17 ` James Almer
2024-04-17 22:13 ` [FFmpeg-devel] FFmpeg table at NAB Thilo Borgmann via ffmpeg-devel
2024-04-21 8:47 ` Rémi Denis-Courmont
2024-04-21 20:25 ` Thilo Borgmann via ffmpeg-devel
2024-04-22 2:02 ` Rémi Denis-Courmont
2024-04-24 6:07 ` Thilo Borgmann via ffmpeg-devel
2024-04-24 6:36 ` [FFmpeg-devel] Cease and desist Rémi Denis-Courmont
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=38bff159-d1d3-40cd-954d-9892b78c0077@gmail.com \
--to=derek.buitenhuis@gmail.com \
--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