From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] [RFC] Cherry picks vs merges Date: Sun, 1 Jun 2025 17:22:22 +0200 Message-ID: <20250601152222.GU29660@pb2> (raw) [-- Attachment #1.1: Type: text/plain, Size: 1802 bytes --] Hi all almpeg is now merged upto 1 months ago. (and since last merge it contains bits of AGPL code) The question now is, how does the community want to proceed from here? I think there are mainly 2 options 1. People review almpeg/master, fix any issues they want fixed, change anything they want changed and then we just "git merge" it. 2a. People cherry pick individual commits one by one and or diff between almpeg and mainline and post these for review like any other patches 2b. People review these patches 2c. patches or almpeg is updated according to reviews and this is repeated until everyone is happy 2d. patches are applied to mainline and the diff between almpeg and mainline decreases. (so one can always consider diff hunks to be things that need to be worked on either update almpeg to mainline or mainline to almpeg) I do intend to post a small set of patches from almpeg so we can see how the cherry picking style method would work. How merging would look you can basically see in almpeg/master already Into which of the 2 options would you be more eager to put your time? (I think it really matters where you want to put your time not so much where you want others to put their time ...) PS: also theres STF, is someone interrested in doing more patch reviews when it is payed ? If so, say something, i think we either way need more reviewers and STF would be one way to incentivize more reviewing PS2: yes we can vote about cherry pick vs merge if people want but i suspect its more a question about will and time than vote. thx -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB What is kyc? Its a tool that makes you give out your real ID, while criminals give out a forged ID card. [-- 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".
next reply other threads:[~2025-06-01 15:22 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-01 15:22 Michael Niedermayer [this message] 2025-06-01 17:12 ` Kieran Kunhya via ffmpeg-devel 2025-06-01 17:27 ` James Almer 2025-06-01 19:23 ` Michael Niedermayer 2025-06-01 19:48 ` compn 2025-06-01 20:01 ` James Almer 2025-06-01 21:31 ` Michael Niedermayer 2025-06-02 4:46 ` Vittorio Giovara 2025-06-02 15:05 ` Michael Niedermayer 2025-06-02 7:41 ` Marton Balint 2025-06-02 8:23 ` softworkz . 2025-06-02 15:28 ` Michael Niedermayer 2025-06-02 15:57 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 15:20 ` compn 2025-06-01 21:55 ` Kieran Kunhya via ffmpeg-devel 2025-06-02 4:36 ` Baptiste Coudurier 2025-06-02 15:38 ` Rémi Denis-Courmont 2025-06-03 13:09 ` Michael Niedermayer 2025-06-03 22:38 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 14:51 ` Michael Niedermayer 2025-06-04 15:00 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 15:35 ` Rémi Denis-Courmont 2025-06-04 18:06 ` Tomas Härdin 2025-06-04 20:42 ` Baptiste Coudurier 2025-06-04 22:41 ` Michael Niedermayer
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=20250601152222.GU29660@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