I was not sure about how to CC the current maintainers via code.f.o so this
is the CC..
-- Forwarded message -
De : toots via ffmpeg-devel
Date: mar. 18 nov. 2025 à 17:02
Subject: [FFmpeg-devel] [PATCH] Add myself as maintainer to the various ogg
files. (PR #20961)
To:
Cc: toots
I like what JB is saying here.
Is there a code of conduct or a set of rules for people representing the
project?
If so, is there an agreed upon procedure to respond to cases where these
are not respected?
This would make the whole matter more consensual and any decision regarding
breaking the ru
On Mon, Oct 20, 2025, 12:51 Tomas Härdin via ffmpeg-devel <
[email protected]> wrote:
> Hi
>
> I'm writing this email to get a feel for how everyone feels about
> making more use of C++ in the codebase. I am only proposing using C++
> *internally*, and only where it makes sense. I am not sug
Hi all,
Thank you so much for taking the time to look into this, Yalda.
I'm glad that you found the changes suitable!
I have looked into the memory leak with the api-dump-stream-meta-test.
The test binary was not written with a continuous http stream in mind so it
needs to be updated to shutdow
Le lun. 29 sept. 2025 à 11:46, Yalda a écrit :
>
> Hi Romain,
>
> My pleasure and thanks for contributing this change.
>
> I was just wanting to know on this line (tagged in PR comments), if
> there are scenarios
> where we may only get one of these blocks on segment change and if we
need to
> als
Le mer. 20 août 2025 à 15:25, Yalda via ffmpeg-devel
a écrit :
> Thanks Romain. I am experimenting with this and trying the patches.
Awesome. Thanks so much for your time!
I have rebased the vorbis header PR against the latest `master` (would
love to call it main).
I have also pushed the next p
