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 via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: Re: [FFmpeg-devel] [POLL][RFC] Merge vs Cherry pick for integration of changes
Date: Sun, 24 Aug 2025 12:59:29 +0200
Message-ID: <20250824105929.GA29660@pb2> (raw)
In-Reply-To: <20250821113202.GH29660@pb2>


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

Hi

On Thu, Aug 21, 2025 at 01:32:02PM +0200, Michael Niedermayer via ffmpeg-devel wrote:
> Hi
> 
> Should we use a Merge or Cherry picks for integrating Pauls work ?
> 
> Following are 2 plans, as we execute either we may run into issues
> and of course adapt them as needed. (or even switch)
> 
> Option M:
>     This would be a merge of pauls last revission before files where
>     switched to GPL and the command line tool to AGPL
> 
>     It would include all changes (except what is intentionally skiped)
>     (This will look similar to how almpeg looks now)
> 
>     Fate tests would be added after the merge where sample media is
>     publically available on our server.
>     Reviews of Individual modules can be done after the merge where
>     people want to do that.
> 
> Option C:
>     Individual Modules (Codecs, Filters, Demuxers) would be submitted
>     as patch(sets)
> 
>     This would include only the picked changes. Changes noone picks and
>     posts would be missing.
> 
>     Each would go through the review process (some likely with "apply
>     after timeout"). And during that review fate tests would be added
>     where public samples are on our server.
> 
> M would likely integrate more changes, C less changes. C may be more work.

"M", (probably) less work than "C" and iam lazy. But 100% happy to change my vote to
     "C", if thats what the majority preferrs

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The difference between a dictatorship and a democracy is that every 4 years
the population together is allowed to provide 1 bit of input to the government.

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

      parent reply	other threads:[~2025-08-24 10:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 11:32 Michael Niedermayer via ffmpeg-devel
2025-08-21 16:56 ` Kieran Kunhya via ffmpeg-devel
2025-08-21 17:53   ` Michael Niedermayer via ffmpeg-devel
2025-08-21 17:58     ` Kieran Kunhya via ffmpeg-devel
2025-08-22 12:29 ` Niklas Haas via ffmpeg-devel
2025-08-22 12:45   ` Diederick C. Niehorster via ffmpeg-devel
2025-08-22 12:59   ` Michael Niedermayer via ffmpeg-devel
2025-08-23  7:09     ` Rémi Denis-Courmont via ffmpeg-devel
2025-08-23 10:58       ` Michael Niedermayer via ffmpeg-devel
2025-08-23 12:59         ` Kieran Kunhya via ffmpeg-devel
2025-08-22 13:45   ` Michael Niedermayer via ffmpeg-devel
2025-08-23 13:20 ` Michael Niedermayer via ffmpeg-devel
2025-08-23 20:33 ` [FFmpeg-devel] Legal Advice Was: " Michael Niedermayer via ffmpeg-devel
2025-08-24  6:53   ` Kieran Kunhya via ffmpeg-devel
2025-08-24 10:56     ` Michael Niedermayer via ffmpeg-devel
2025-08-24 11:11       ` Kieran Kunhya via ffmpeg-devel
2025-08-24 12:08         ` Michael Niedermayer via ffmpeg-devel
2025-08-24 12:17           ` Kieran Kunhya via ffmpeg-devel
2025-08-24 10:59 ` Michael Niedermayer via ffmpeg-devel [this message]

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=20250824105929.GA29660@pb2 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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