Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
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
Date: Thu, 8 May 2025 01:21:48 +0200
Message-ID: <20250507232148.GM29660@pb2> (raw)
In-Reply-To: <DM8P223MB036509378857E4B3BC0743A1BA88A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 1644 bytes --]

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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2025-05-07 23:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 11:58 Andreas Rheinhardt
2025-05-07 17:57 ` softworkz .
2025-05-07 18:29   ` James Almer
2025-05-07 18:54     ` softworkz .
2025-05-07 19:14       ` softworkz .
2025-05-07 23:21         ` Michael Niedermayer [this message]
2025-05-07 23:38           ` softworkz .
2025-05-16 14:06 ` Andreas Rheinhardt
2025-05-16 14:52   ` Ramiro Polla
2025-05-16 18:39     ` Andreas Rheinhardt

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=20250507232148.GM29660@pb2 \
    --to=michael@niedermayer.cc \
    --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