Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg
Date: Sun, 25 May 2025 23:29:45 +0100
Message-ID: <CABGuwEmtUvwHyxP5r7ap3bRWg6VKc2fzT5zFxXheCOEDghNHiw@mail.gmail.com> (raw)
In-Reply-To: <20250525192252.GM29660@pb2>

Hi Michael,

Here is how this should be handled.

"Hi Paul,

I'm sorry for aggressively trying to force SDR into the FFmpeg project
over a period of several weeks in spite of objections from you and the
community causing you to leave.
FFmpeg is now a better community* and we would love it if you could come back.

Regards,
Michael Niedermayer
"
* Narrator: It is not a better community

Regards,
Kieran Kunhya

On Sun, May 25, 2025 at 8:23 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi all
>
> Id like to announce that ive setup a repository to merge pauls work of
> the last 2 years.
>
> * Currently ive merged everything up to first february 2025
> * all fate tests pass
> * Some filters and decoders where split in 2 versions
>     thats because either teh added chanegs are buggy, break API/cmd line interface
>     or plain the 2 versions are actively developed and too diverged
>
> Note the license of this code is a bit wonky. The files have one
> license and theres another one in LICENSE.md.
> While I belives legally this allows one to choose either. I suggest
> you check this with a lawyer.
>
> git@git.ffmpeg.org:almpeg
>
> all ffmpeg developers should have write access to it (if you dont,
> send me private mail/ping and expect 1-2 days to fix)
>
> If you want to fix any mistakes in this, thats welcome!
> currently gitlog mails are just sent to me, this can be changed if people want
>
> Now, what is this good for ?
> Once teh merges match the current date, we can either
> * just merge it (with 0 conflicts)
> * cherry pick from it easily (its closer to FFmpeg)
>     We can also for the cherry picking easily collaborate
>     using the almpeg repository and commit requested changes from
>     patch review to it
>
> PS: today it seems a merge between master and almpeg has just 22 conflicts
> a direct merge from pauls code with master has 1145 conflicts
>
> thx
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Many things microsoft did are stupid, but not doing something just because
> microsoft did it is even more stupid. If everything ms did were stupid they
> would be bankrupt already.
> _______________________________________________
> 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".
_______________________________________________
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-05-25 22:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 19:22 Michael Niedermayer
2025-05-25 22:29 ` Kieran Kunhya via ffmpeg-devel [this message]
2025-05-25 23:11   ` compn
2025-05-26  8:00 ` Rémi Denis-Courmont
2025-05-26  9:27   ` softworkz .
2025-05-26 11:26     ` Rémi Denis-Courmont
2025-05-26 11:44       ` softworkz .
2025-05-26 11:37     ` Michael Niedermayer
2025-05-26 11:49       ` softworkz .
2025-05-26 12:21       ` softworkz .
2025-05-26 17:21         ` Michael Niedermayer
2025-05-26 17:56           ` softworkz .
2025-05-26 20:59             ` Michael Niedermayer
2025-05-26 21:10               ` softworkz .
2025-05-26 21:35                 ` softworkz .
2025-05-26 21:56           ` softworkz .
2025-05-26 16:36 ` Michael Niedermayer
2025-05-28  1:09   ` 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=CABGuwEmtUvwHyxP5r7ap3bRWg6VKc2fzT5zFxXheCOEDghNHiw@mail.gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    /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