From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Stefano Sabatini <stefasab@gmail.com>
Subject: Re: [FFmpeg-devel] [RFC] Shaping the AVTextFormat API Surface
Date: Sat, 3 May 2025 08:55:42 +0000
Message-ID: <DM8P223MB0365C64B0C3BEB1C659F4DFABA8C2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB036544510099A04264475BE1BA812@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of softworkz .
> Sent: Dienstag, 29. April 2025 01:24
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Shaping the AVTextFormat API Surface
>
>
>
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Stefano
> > Sabatini
> > Sent: Dienstag, 29. April 2025 00:27
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [RFC] Shaping the AVTextFormat API Surface
> >
> > On date Sunday 2025-04-27 17:54:21 +0000, softworkz . wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > > > Stefano Sabatini
> > > > Sent: Sonntag, 27. April 2025 12:42
> > > > To: FFmpeg development discussions and patches <ffmpeg-
> > > > devel@ffmpeg.org>
> > > > Subject: Re: [FFmpeg-devel] [RFC] Shaping the AVTextFormat API Surface
> > > >
>
> [..]
Hello Stefano,
I have five new commits for this:
fftools/textformat: Rename variables wctx to tctx
fftools/textformat: Cleanup unneeded includes
fftools/textformat: Add validation for TextFormat API
fftools/textformat: Add validation for AVTextWriter implementations
fftools/textformat: Add validation for AVTextFormatter implementations
Yet I don't believe it makes sense to squash them once again back into
commits that you have reviewed already, they are much easier to review
separately.
So, if you would agree, I'd merge the current patchset first (once
Michael confirms the zlib issue being resolved) and send the new commits
as a new patchset then?
Thanks,
sw
_______________________________________________
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-03 8:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 4:20 softworkz .
2025-04-24 14:47 ` [FFmpeg-devel] On errors, asserts and crashing (was: Shaping the AVTextFormat API Surface) Nicolas George
2025-04-25 13:05 ` softworkz .
2025-04-25 14:04 ` Nicolas George
2025-04-25 14:37 ` softworkz .
2025-04-25 14:41 ` Nicolas George
2025-04-25 14:53 ` softworkz .
2025-04-25 14:43 ` [FFmpeg-devel] On errors, asserts and crashing James Almer
2025-04-25 14:49 ` softworkz .
2025-04-25 16:04 ` Michael Niedermayer
2025-04-24 17:12 ` [FFmpeg-devel] [RFC] Shaping the AVTextFormat API Surface Nicolas George
2025-04-25 13:24 ` softworkz .
2025-04-25 13:32 ` softworkz .
2025-04-25 14:05 ` Nicolas George
2025-04-25 14:26 ` softworkz .
2025-04-27 10:07 ` Stefano Sabatini
2025-04-29 8:30 ` Nicolas George
2025-04-29 18:07 ` softworkz .
2025-04-30 2:56 ` softworkz .
2025-05-04 15:32 ` Stefano Sabatini
2025-05-04 20:38 ` softworkz .
2025-05-05 14:32 ` Nicolas George
2025-05-06 10:45 ` softworkz .
2025-05-07 23:18 ` Stefano Sabatini
2025-04-24 18:34 ` Rémi Denis-Courmont
2025-04-25 13:16 ` softworkz .
2025-04-27 10:42 ` Stefano Sabatini
2025-04-27 17:54 ` softworkz .
2025-04-28 22:26 ` Stefano Sabatini
2025-04-28 23:24 ` softworkz .
2025-05-03 8:55 ` softworkz . [this message]
2025-05-07 23:30 ` Stefano Sabatini
2025-05-07 23:42 ` softworkz .
2025-05-08 21:26 ` Stefano Sabatini
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=DM8P223MB0365C64B0C3BEB1C659F4DFABA8C2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=stefasab@gmail.com \
/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