From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, Marth64 <marth64@proxyid.net>
Subject: Re: [FFmpeg-devel] [PATCH v11 0/6] RCWT Closed Captions demuxer (v11)
Date: Tue, 2 Apr 2024 14:14:39 -0500
Message-ID: <CA+28BfB6L5CH0e_TDZ+PpyjJuBwuToxcE85=STdQpJ+ob0sRxQ@mail.gmail.com> (raw)
In-Reply-To: <ZgxKk1vzTIHMKGII@mariano>
Thank you Stefano & all who helped facilitate this through.
_______________________________________________
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".
prev parent reply other threads:[~2024-04-02 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 5:24 Marth64
2024-04-02 5:24 ` [FFmpeg-devel] [PATCH v11 1/6] avformat/subtitles: extend ff_subtitles_queue_insert() to support not yet available events Marth64
2024-04-02 5:24 ` [FFmpeg-devel] [PATCH v11 2/6] avformat/rcwtdec: add RCWT Closed Captions demuxer Marth64
2024-04-02 5:24 ` [FFmpeg-devel] [PATCH v11 3/6] avformat/rcwtenc: don't assume .bin extension Marth64
2024-04-02 5:24 ` [FFmpeg-devel] [PATCH v11 4/6] avformat/rcwtenc: remove repeated documentation Marth64
2024-04-02 5:24 ` [FFmpeg-devel] [PATCH v11 5/6] doc/muxers: refresh the RCWT muxer's doc to be consistent with the demuxer Marth64
2024-04-02 5:24 ` [FFmpeg-devel] [PATCH v11 6/6] doc/indevs: update CC extraction example to use RCWT muxer Marth64
2024-04-02 18:12 ` [FFmpeg-devel] [PATCH v11 0/6] RCWT Closed Captions demuxer (v11) Stefano Sabatini
2024-04-02 19:14 ` Marth64 [this message]
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='CA+28BfB6L5CH0e_TDZ+PpyjJuBwuToxcE85=STdQpJ+ob0sRxQ@mail.gmail.com' \
--to=marth64@proxyid.net \
--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