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: Sat, 23 Aug 2025 15:20:25 +0200
Message-ID: <20250823132025.GT29660@pb2> (raw)
In-Reply-To: <20250821113202.GH29660@pb2>


[-- Attachment #1.1: Type: text/plain, Size: 1645 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)

If neither Cherry picking nor Merging is choosen then I will remove
my STF proposal about that work before 1. September (unless the deadline
is extended).

Without that funding, i cannot offer going through individual modules.
That means someone else would need to volunteer doing this work
to have the "Cherry pick" option in the future.
(also consider code divergence with a future funding round)

For the "Merge" option, similarly, the loss of STF funding would mean a loss
of (funded) "per module" work. "Merge" will stay available from me but without
per module work. (someone else would have to do per module work, or no per module
work would be done)

OTOH with the Integration of pauls code, i will spend more time on FFmpeg
in the next 12 months, i would continue doing the fuzzing work as good as i
can and i will try to get the 8.1 release done in the next 3 months if people
want that.
Without the integration of the code, I will likely loose alot of my motivation
to contribute.

I hope "D" (if its choosen) will stand for Discussion and not Decline or even
eventual Death of FFmpeg.

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus

[-- 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-23 13:20 UTC|newest]

Thread overview: 13+ 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 [this message]
2025-08-23 20:33 ` [FFmpeg-devel] Legal Advice Was: " Michael Niedermayer via ffmpeg-devel

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=20250823132025.GT29660@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