Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Yalda <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Tristan Matthews <httamt@protonmail.com>
Subject: Re: [FFmpeg-devel] Pushing without approval avfilter/vf_vignette: use AVFilterContext for logging
Date: Tue, 12 Aug 2025 11:15:29 -0500
Message-ID: <CAAhd_PUZrgk=HvRBKnQbwyhuTroD=H+Y9=PNREnyGFO3u-MzJQ@mail.gmail.com> (raw)
In-Reply-To: <QGjYISqYgKUcftBO9xGNu6jQzSFUIUJlazlXVFtG5WCndj2MnfWpwwP43rpbyYotzhaBmutKhzPrSTtjSbUvpglIPJBA8vVYzbmVNe4ekaU=@protonmail.com>

Nicolas George:
> Approval full stop is [********]. The only approval worth something comes
> from somebody who knows the code.
>
> How do you know that approval was worth anything?
>
> So as a default, they are maintained by whoever maintains libavfilter

----

I was the one who approved this PR.

I’ve had a high tolerance for remarks like yours, but I will not stand
by anymore as you question the competence of contributors without cause,
a pattern which does nothing but drive people away.

For the record:
1) I reviewed the PR in full, understood the changes, and stand by my
approval.

2) Gatekeeping over trivial or clearly beneficial patches harms the project
and drives contributors away. The only “gain” from it is polishing one’s
own ego.

3) I do not give blind approvals. I am more than capable of understanding,
implementing, and approving changes at and beyond the scope here.
Suggesting otherwise is an insult to my intelligence which I will not
accept.

And since we are being direct: your recent contributions to this project
consist largely of criticizing others without offering substantive
technical work yourself. Even minor contributors today are more in tune
with the project’s direction.

If there are genuine, technical objections to this PR, let’s address them
directly. Otherwise, undermining contributors without adding value only
hurts FFmpeg and the community at large.
_______________________________________________
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-12 16:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250812090205.A5F4D68B0ED@ffbox0-bg.ffmpeg.org>
2025-08-12  9:16 ` Nicolas George
2025-08-12  9:34   ` Niklas Haas
2025-08-12  9:35     ` Niklas Haas
2025-08-12  9:38     ` Gyan Doshi
2025-08-12  9:51       ` Niklas Haas
2025-08-12  9:53         ` Nicolas George
2025-08-12 10:04           ` Niklas Haas
2025-08-12 17:20             ` Nicolas George
2025-08-12 15:57           ` James Almer
2025-08-12 17:13             ` Nicolas George
2025-08-12 12:35         ` Tristan Matthews via ffmpeg-devel
2025-08-12 15:59           ` Kacper Michajlow
2025-08-12 16:02             ` Niklas Haas
2025-08-12 21:22             ` Jean-Baptiste Kempf
2025-08-13  0:43               ` Michael Niedermayer
2025-08-13  0:57                 ` Timo Rothenpieler
2025-08-13 10:42                   ` Michael Niedermayer
2025-08-12 16:15           ` Yalda [this message]
2025-08-12 17:08             ` Nicolas George
2025-08-12 17:24               ` Yalda
2025-08-12  9:50     ` Nicolas George

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='CAAhd_PUZrgk=HvRBKnQbwyhuTroD=H+Y9=PNREnyGFO3u-MzJQ@mail.gmail.com' \
    --to=marth64@proxyid.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=httamt@protonmail.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