From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Revert "forgejo/lint_commit_msg: add script for commit message linting" (PR #20147)
Date: Thu, 7 Aug 2025 10:45:38 +0200
Message-ID: <aJRnsonF837aTW8D@phare.normalesup.org> (raw)
In-Reply-To: <20250806224741.7A66B68CC6E@ffbox0-bg.ffmpeg.org>
michaelni (HE12025-08-07):
> PR #20147 opened by michaelni
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20147
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20147.patch
>
> This should be done by fate.
> This script already blocks security fixes (https://code.ffmpeg.org/FFmpeg/FFmpeg/actions/runs/1046/jobs/0)
>
> IMHO its not good
> 1. to add commit message formating rules, never discussed or agreed
> 2. to expect developers to push commits trial and error style, make fate
> can test this already and tell the devlopers before pushing, saving him
> time
>
> This reverts commit cc6ad703b41e318bd1e4cb6196defaf505dbfea3.
LGTM.
We certainly are not at the point where policies affecting the whole
project can be enacted without discussion on the mailing-list.
Regards,
--
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 parent reply other threads:[~2025-08-07 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250806224741.7A66B68CC6E@ffbox0-bg.ffmpeg.org>
2025-08-07 8:45 ` Nicolas George [this message]
2025-08-06 22:47 michaelni
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=aJRnsonF837aTW8D@phare.normalesup.org \
--to=george@nsup.org \
--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