From: Lynne <dev@lynne.ee>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 0/5] doc/developer: Add subsection about patch submission via FFstaging
Date: Thu, 8 May 2025 13:59:32 +0200
Message-ID: <d33df924-cc4c-4fd5-8fc7-1c3e59f42c31@lynne.ee> (raw)
In-Reply-To: <DM8P223MB03653ABE0E0E0736E0224387BA8BA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 2163 bytes --]
On 08/05/2025 13:33, softworkz . wrote:
>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
>> Sent: Donnerstag, 8. Mai 2025 13:20
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] [PATCH 0/5] doc/developer: Add subsection about
>> patch submission via FFstaging
>>
>> On 08/05/2025 12:22, ffmpegagent wrote:
>>> Signed-off-by: softworkz softworkz@hotmail.com
>>>
>>> softworkz (5):
>>> doc/developer: Move checklist into Submitting Patches chapter
>>> doc/developer: Move codecs/formats checklist into Development Policy
>>> chapter
>>> doc/developer: Reorder Submission procedures content
>>> doc/developer: Merge Review paragraphs and deduplicate
>>> doc/developer: Add subsection about patch submission via FFstaging
>>>
>>> doc/developer.texi | 234 ++++++++++++++++++++++++---------------------
>>> 1 file changed, 127 insertions(+), 107 deletions(-)
>>>
>>>
>>> base-commit: 1b643e3f65d75a4e6a25986466254bdd4fc1a01a
>>> Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-
>> 76%2Fsoftworkz%2Fsubmit_website_update-v1
>>> Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-
>> 76/softworkz/submit_website_update-v1
>>> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/76
>>
>> No.
>> We're not going to accept patches via github. Not when we're going to
>> enable the forgejo instance soon, as there's an agreement.
>
>
> This is not about patch acceptance on GitHub. It doesn't stand in contradiction
> or competition to ForgeJo (which I do support moving to).
>
> It is simply a tool for sending patches to the mailing list. It has no value
> outside of the ML workflow. The service is public, everybody can use it,
> patches arrive on the ML - nobody needs to care where they're coming from
> or how they were generated.
>
> All my patches are going this route, btw.
You're free to use any tool you like. But this patchset makes it official.
Pointing out that it's just a service or a tool that anyone can run is
in conflict with the fact that.
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 637 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 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 11:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 10:22 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
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 [this message]
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=d33df924-cc4c-4fd5-8fc7-1c3e59f42c31@lynne.ee \
--to=dev@lynne.ee \
--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