Re: [FFmpeg-devel] [PATCH 01/21] avutil/avassert: Add av_unreachable and av_assume() macros

["softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> Niedermayer
> Sent: Donnerstag, 8. Mai 2025 01:22
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 01/21] avutil/avassert: Add av_unreachable
> and av_assume() macros
> 
> 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)

It depends on how far or close we are to move away from the
ML, as there can be only one "source of truth", where all patches 
are moving through.
The setup on ffstaging is simply a tool that is useful for submitting
patches to the ML without the trouble (for some like me) of using
git send-email. It will become obsolete as soon as the ML won't be
the central hub for patches anymore.

But for the time being, I can surely propose a paragraph with a 
description similar to the above.
I somehow assumed that most (regulars at least) would already know
what it is and what it does, but from Jame's response I've seen 
that I was a wrong, so yea, let's do this.

Best,
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".