From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
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: Wed, 7 May 2025 17:57:18 +0000
Message-ID: <DM8P223MB036583FA7E110889B9112C41BA88A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <GV1P250MB0737FD24CB587A07E48044308F88A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Andreas
> Rheinhardt
> Sent: Mittwoch, 7. Mai 2025 13:59
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: [FFmpeg-devel] [PATCH 01/21] avutil/avassert: Add av_unreachable and
> av_assume() macros
>
> Patches attached.
>
> - Andreas
Hi Andreas,
from https://ffmpeg.org/developer.html#Submitting-patches-1
"..ensure the correct mime type is used (text/x-diff or text/x-patch or at least text/plain) and that only one patch is inline or attached per mail."
I'm saying that because the way you are submitting, Patchwork only ever recognizes the first attached patch, so - in this case - the remaining 20 patches are not checked by the CI runs.
It's also difficult to review patches that are submitted in this way, even more difficult to respond, as that requires to copy the patch into a text editor first, in order to add some synthetic quote marks ("> ") and when replying, it isn't clear to which of the patches the reply is corresponding to.
As long as there's no migration to a better way, why not try out making PRs to https://github.com/ffstaging/FFmpeg?
AFAIC, I'm quite happy with that route, it's totally painless (no SMTP trouble, no manual sending).
Best regards,
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-07 17:57 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 . [this message]
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
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=DM8P223MB036583FA7E110889B9112C41BA88A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--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