From: Niklas Haas <ffmpeg@haasn.xyz> To: ffmpeg-devel@ffmpeg.org Cc: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] Pushing without approval avfilter/vf_vignette: use AVFilterContext for logging Date: Tue, 12 Aug 2025 11:34:08 +0200 Message-ID: <20250812113408.GB24045@haasn.xyz> (raw) In-Reply-To: <aJsGYw51wpUVurHT@phare.normalesup.org> On Tue, 12 Aug 2025 11:16:19 +0200 Nicolas George <george@nsup.org> wrote: > ffmpeg-git@ffmpeg.org (HE12025-08-12): > > Author: Niklas Haas <git@haasn.dev> > > AuthorDate: Mon Aug 11 15:57:24 2025 +0200 > > Commit: Niklas Haas <ffmpeg@haasn.dev> > > CommitDate: Tue Aug 12 09:01:39 2025 +0000 > > Pushing after less than 24 hours without approval by the maintainer is > absolutely unacceptable, forge or no forge, and a spit in my face for > the time I invested into starting to look at the code, thankfully > limited. In https://ffmpeg.org/developer.html#Patch-review-process it says: > After a patch is approved it will be committed to the repository. I don't see anything about a time-frame requirement here. That said, maybe we should adopt one, especially now that we actually receive reviews in a timely manner thanks to the adoption of forgejo. Perhaps we adopt the VLC model, which is: - If a PR has received no activity for 3 days - AND it has at least one approval - AND it passes all CI checks then it will be merged automatically, by a bot. > > Never do that again. > > -- > Nicolas George _______________________________________________ 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".
next prev parent reply other threads:[~2025-08-12 9:34 UTC|newest] Thread overview: 17+ 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 [this message] 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 16:15 ` Yalda 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=20250812113408.GB24045@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --cc=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