From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/bitstream_filters: add filter_units practical examples for removing closed captions
Date: Sat, 9 Dec 2023 21:17:24 -0600
Message-ID: <CA+28BfB+oFTvBdeZqvpG_PYNV93sO=u2y_eYwayghz78dbsODA@mail.gmail.com> (raw)
In-Reply-To: <9b20bf41-8262-40e8-9ee3-806549494c44@gmail.com>
Thank you!
On Sat, Dec 9, 2023 at 9:06 PM Leo Izen <leo.izen@gmail.com> wrote:
> On 12/9/23 20:35, Marth64 wrote:
> > ---
> > doc/bitstream_filters.texi | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> >
>
> Make sure when you generate the second version of a patch with git
> format-patch you pass the -v2 argument, e.g.
>
> git format-patch -v2 -o outgoing/ master
>
> Otherwise it can get a little bit difficult for reviewers to track the
> versions. I have no comments on the patch itself, in either direction.
>
> - Leo Izen (Traneptora)
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2023-12-10 3:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 19:31 Marth64
2023-12-10 0:53 ` Stefano Sabatini
2023-12-10 1:26 ` Marth64
2023-12-10 1:35 ` Marth64
2023-12-10 3:06 ` Leo Izen
2023-12-10 3:17 ` Marth64 [this message]
2023-12-11 23:29 ` Stefano Sabatini
2023-12-11 16:33 ` [FFmpeg-devel] [PATCH v2] " Marth64
2023-12-11 20:27 ` Mark Thompson
2024-03-10 1:56 [FFmpeg-devel] [PATCH] " Marth64
2024-03-10 14:56 ` Stefano Sabatini
2024-03-10 15:29 ` Marth64
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+28BfB+oFTvBdeZqvpG_PYNV93sO=u2y_eYwayghz78dbsODA@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