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 <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] postproc/postprocess_template: Fix reading uninitialized pixels in dering_C()
Date: Tue, 22 Apr 2025 21:54:02 +0200
Message-ID: <20250422195402.GO4991@pb2> (raw)
In-Reply-To: <CABGuwEm7qiVZ-5hNip1k0eEVF7jc_B9OLxFFzTKCM7JKrGT_tA@mail.gmail.com>


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

Hi Kieran

On Tue, Apr 22, 2025 at 01:23:19AM -0100, Kieran Kunhya via ffmpeg-devel wrote:
> On Tue, 22 Apr 2025, 00:44 Michael Niedermayer, <michael@niedermayer.cc>
> wrote:
> 
> > Sponsored-by: Sovereign Tech Fund
> > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> >
> 
> I thought we decided postproc work in STF wasn't going to happen?

I thought i am going to do the work for the 2 remaining milestones
and I will donate the money for these 2 milestones to FFmpeg.
I thought everyone was happy with that.

If the FFmpeg community prefers, we can explore the posibility to
change the contracts to remove the postproc work.
This would mean that i will do the work exactly the same way
and FFmpeg would then get nothing.
Also iam not sure how STF would see this if we told them that
we will do the work but want it taken out of the contract so we
receive no money for it.


> 
> Note that the STF wiki doesn't mention anything about bugfixes to
> libpostproc.

The bugfix was required for blocktest to work. And teh wiki lists
"Have functioning build and selftest systems"

But ive removed the "Sponsored-by: Sovereign Tech Fund" from the
commit message.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

He who knows, does not speak. He who speaks, does not know. -- Lao Tsu

[-- 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-04-22 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  1:43 Michael Niedermayer
2025-04-22  2:23 ` Kieran Kunhya via ffmpeg-devel
2025-04-22 19:54   ` Michael Niedermayer [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=20250422195402.GO4991@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