From: Devin Heitmueller via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Yalda <marth64@proxyid.net>
Cc: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
Devin Heitmueller <devin.heitmueller@ltnglobal.com>
Subject: [FFmpeg-devel] Re: [GSoC 2026] Qualification Task – SubViewer Decoder Patch
Date: Wed, 11 Feb 2026 08:51:25 -0500
Message-ID: <CAHGibzFaODm0GVRFeFkP09Ad722UiLSeS5qxkQ4xLS4Ajv=r0g@mail.gmail.com> (raw)
In-Reply-To: <CAAhd_PWBrG2S6NTvcLZg7WkwHC=zccLn0yVY-qDypmNXw=+vcg@mail.gmail.com>
On Tue, Feb 10, 2026 at 10:25 AM Yalda <marth64@proxyid.net> wrote:
>
> Hello Devin,
>
> Thank you for the feedback. I am good with a 608->708 BSF being added
> to the bucket list.
> In order for the project to be accepted, I was asked to list/provide a
> backup mentor. Would you be able to assist in the capacity of backup
> mentor?
Sure, that's fine.
Devin
--
Devin Heitmueller, Senior Software Engineer
LTN Global Communications
o: +1 (301) 363-1001
w: https://ltnglobal.com e: devin.heitmueller@ltnglobal.com
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2026-02-11 13:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 14:43 [FFmpeg-devel] " Nariman Sayed via ffmpeg-devel
2026-01-26 18:39 ` [FFmpeg-devel] " Yalda via ffmpeg-devel
2026-01-26 19:09 ` Nariman Sayed via ffmpeg-devel
2026-01-26 19:21 ` Devin Heitmueller via ffmpeg-devel
2026-01-26 20:15 ` Yalda via ffmpeg-devel
2026-01-28 15:27 ` Devin Heitmueller via ffmpeg-devel
2026-01-31 0:40 ` Yalda via ffmpeg-devel
2026-01-31 15:00 ` Devin Heitmueller via ffmpeg-devel
2026-02-10 15:24 ` Yalda via ffmpeg-devel
2026-02-11 13:51 ` Devin Heitmueller via ffmpeg-devel [this message]
2026-02-17 20:56 ` Nariman Sayed via ffmpeg-devel
2026-02-18 3:28 ` Yalda 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='CAHGibzFaODm0GVRFeFkP09Ad722UiLSeS5qxkQ4xLS4Ajv=r0g@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=devin.heitmueller@ltnglobal.com \
--cc=marth64@proxyid.net \
/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