From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Pushing without approval avfilter/vf_vignette: use AVFilterContext for logging
Date: Wed, 13 Aug 2025 12:42:27 +0200
Message-ID: <20250813104227.GN29660@pb2> (raw)
In-Reply-To: <e4b2a40a-14ec-4128-9d07-df2b5076b565@rothenpieler.org>
[-- Attachment #1.1: Type: text/plain, Size: 2106 bytes --]
On Wed, Aug 13, 2025 at 02:57:02AM +0200, Timo Rothenpieler wrote:
> On 8/13/2025 2:43 AM, Michael Niedermayer wrote:
> > Hi
> >
> > On Tue, Aug 12, 2025 at 11:22:44PM +0200, Jean-Baptiste Kempf wrote:
> > > On Tue, 12 Aug 2025, at 17:59, Kacper Michajlow wrote:
> > > > Because of course there is homer-bot... I think everyone seen
> > > > marge-bot too https://github.com/smarkets/marge-bot (also GitLab
> > > > specific)
> > >
> > > Be careful, those are 2 very different bots.
> > >
> > > Marge bot, is a bot to avoid the fight for all the MR to be rebased before merging them.
> > > You assign to Marge and it handles the merging at the best time, to save time and cycles to everyone.
> > >
> > > Homer bot, is a bot to explain clearly the workflow to help what should be mergeable, to avoid exactly the issue we just saw, or the issues we saw in the past on the ML, where people wanted to merge their code quicker than some reviewers were.
> > >
> > > Homer is configurable, but the idea is basically:
> > > - if you are dev/maintainer, and noone comments for x days, you can merge
> > > - if you are external/no commit access, you need at least one OK and y days, and one can merge
> >
> > > - any discussion/thread opened blocks any merging, which allows someone to open a thread to say "I'm reviewing", "I have a doubt"
> >
> > Theres a cancel automerge button in forgejo
>
> The automerging in Forgejo is not even close to what those bots do.
> It's simply an automatism for "Once all checks complete, and it still
> applies cleanly, merge it".
>
> It does no CI checks again on the final state or anything, which a merge-bot
> implementing merge trains/a merge queue would do.
You misunderstand what i meant
I meant that sending "any reply" causes merging to be blocked is not great design
because not every person writing a reply wants to block the merge
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Republics decline into democracies and democracies degenerate into
despotisms. -- Aristotle
[-- 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".
next prev parent reply other threads:[~2025-08-13 10:42 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 [this message]
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=20250813104227.GN29660@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