On Wed, May 07, 2025 at 07:14:04PM +0000, softworkz . wrote: [...] > > > > As long as there's no migration to a better way, why not try out making > > PRs > > > to https://github.com/ffstaging/FFmpeg? > > > > > > I doubt "ffstaging" is affiliated with the project in any capacity. > > > > Hi James, > > > > it works like this: > > > > - You make a PR to https://github.com/ffstaging/FFmpeg > > - You make a comment with "/submit" > > - The PR will be submitted to the ML as regular patches > > More specifics: > > - The PR message is sent as the cover-letter text [Patch 0/n] > Markdown is converted to ASCII > > - Commit messages are checked for compliance > > - CI builds are run on the last commit (yet you can submit > without waiting) > > - To submit new versions of a patchset, simply force-push to > your PR branch and comment "/submit" again. > The patchset will automatically be submitted as a new version > (v2, v3, etc.) > > - Comments made on the ML are automatically mirrored back as PR > comments on GH > > - Cover-letters sent to the ML include a range-diff, showing > the changes from the previous version > They also include Git links to directly check out the patchset
Should this be added to doc/developer.texi ? (which shows up as https://ffmpeg.org/developer.html) We also should put forgejo in there too probably thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB For a strong democracy, genuine criticism is necessary, allegations benefit noone, they just cause unnecessary conflicts. - Narendra Modi
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
