From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 5/5] doc/developer: Add subsection about patch submission via FFstaging
Date: Thu, 8 May 2025 09:40:09 -0300
Message-ID: <e859aa5b-445d-4b69-a69f-86a9b097df7c@gmail.com> (raw)
In-Reply-To: <c8dba13b924ad3ede0a2f3ba1227f2e3e8a5a6bd.1746699749.git.ffmpegagent@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1421 bytes --]
On 5/8/2025 7:22 AM, softworkz wrote:
> From: softworkz <softworkz@hotmail.com>
>
> Signed-off-by: softworkz <softworkz@hotmail.com>
> ---
> doc/developer.texi | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 145b57b249..a3ae9e6973 100644
> --- a/doc/developer.texi
> +++ b/doc/developer.texi
> @@ -923,6 +923,22 @@ git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml -
> Now you'll just need to open the eml file with the email application
> and execute 'Send'.
>
> +@subsection FFstaging: Automated GitHub PR to Mailing List submission
> +
> +This is an easy way which doesn't require writing Git commands or SMTP
> +configuration. Basically, it works like this:
> +
> +@itemize @bullet
> +@item
> +You make a GitHub Pull Request on https://github.com/ffstaging/FFmpeg
> +@item
> +You make a comment with "/submit"
> +@item
> +The PR will be submitted to the FFmpeg Mailing List as regular patches
> +@end itemize
> +
> +More details can be found on the Wiki page of the GitHub repository:
> +https://github.com/ffstaging/FFmpeg/wiki
>
> @chapter Patch review process
NAK.
This is not part of our infra. We had a meltdown of people complaining
about stuff like this months ago, citing the xz backdoor and social
engineering, so this is absolutely not ok.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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".
next prev parent reply other threads:[~2025-05-08 12:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 10:22 [FFmpeg-devel] [PATCH 0/5] " ffmpegagent
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 1/5] doc/developer: Move checklist into Submitting Patches chapter softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 2/5] doc/developer: Move codecs/formats checklist into Development Policy chapter softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 3/5] doc/developer: Reorder Submission procedures content softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 4/5] doc/developer: Merge Review paragraphs and deduplicate softworkz
2025-05-08 10:22 ` [FFmpeg-devel] [PATCH 5/5] doc/developer: Add subsection about patch submission via FFstaging softworkz
2025-05-08 12:40 ` James Almer [this message]
2025-05-08 12:55 ` softworkz .
2025-05-08 11:13 ` [FFmpeg-devel] [PATCH 0/5] " softworkz .
2025-05-08 11:20 ` Lynne
2025-05-08 11:33 ` softworkz .
2025-05-08 11:59 ` Lynne
2025-05-08 12:26 ` softworkz .
2025-05-08 12:36 ` Lynne
2025-05-08 12:47 ` Nicolas George
2025-05-08 13:12 ` softworkz .
2025-05-09 10:17 ` softworkz .
2025-05-13 18:05 ` [FFmpeg-devel] [PATCH v2 0/4] doc/developer: Restructure docs about patch submission ffmpegagent
2025-05-13 18:05 ` [FFmpeg-devel] [PATCH v2 1/4] doc/developer: Move checklist into Submitting Patches chapter softworkz
2025-05-13 18:05 ` [FFmpeg-devel] [PATCH v2 2/4] doc/developer: Move codecs/formats checklist into Development Policy chapter softworkz
2025-05-13 18:05 ` [FFmpeg-devel] [PATCH v2 3/4] doc/developer: Reorder Submission procedures content softworkz
2025-05-13 18:05 ` [FFmpeg-devel] [PATCH v2 4/4] doc/developer: Merge Review paragraphs and deduplicate softworkz
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=e859aa5b-445d-4b69-a69f-86a9b097df7c@gmail.com \
--to=jamrial@gmail.com \
--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