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: Mon, 25 Aug 2025 14:04:15 +0200
Message-ID: <20250825120415.GE29660@pb2> (raw)
In-Reply-To: <20250824105929.GA29660@pb2>


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

Hi all

On Sun, Aug 24, 2025 at 12:59:29PM +0200, Michael Niedermayer via ffmpeg-devel wrote:
[...]
> > Option M:
> >     This would be a merge of pauls last revission before files where
> >     switched to GPL and the command line tool to AGPL
[...]
> > 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

Id like to change my choice from "M" to "C" after hearníng the oppinions of
several developers. It seems most people prefer integrating the modules under
GPLv3+ and that is easier with cherry picks than a true merge
Of course as before iam perfectly happy with "M"

thx

[..]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Modern terrorism, a quick summary: Need oil, start war with country that
has oil, kill hundread thousand in war. Let country fall into chaos,
be surprised about raise of fundamantalists. Drop more bombs, kill more
people, be surprised about them taking revenge and drop even more bombs
and strip your own citizens of their rights and freedoms. to be continued

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

      reply	other threads:[~2025-08-25 12:04 UTC|newest]

Thread overview: 22+ 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-25  4:37         ` Baptiste Coudurier via ffmpeg-devel
2025-08-25  5:37           ` Kieran Kunhya via ffmpeg-devel
2025-08-24 10:59 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-08-25 12:04   ` 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=20250825120415.GE29660@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