Re: git: 68df49bce28c - main - =?utf-8?Q?www/forgejo: Update 7.0.12 =E2=86=92 7.0.13 (fixes security vulnerabiliti=Q?www/forgejo: Update 7.0.12 =E2=86=92 7.0.13 (fixes security vulnerabiliti=
Date: Mon, 10 Feb 2025 17:36:02 UTC
On 10/02/25 14:14, Mathieu Arnold wrote: > Le Mon, Feb 10, 2025 at 03:32:12PM +0100, Fernando Apesteguía a écrit : >> El lun, 10 feb 2025, 15:05, Alexey Dokuchaev <danfe@freebsd.org> escribió: >> >>> On Mon, Feb 10, 2025 at 01:27:28PM +0100, Fernando Apestegu??a wrote: >>>> El lun, 10 feb 2025, 13:24, Vladimir Druzenko escribi??: >>>>> es)?= >>>>> MIME-Version: 1.0 >>>>> Content-Type: text/plain; charset=utf-8 >>>>> Content-Transfer-Encoding: 8bit >>>>> X-Git-Committer: vvd >>>>> X-Git-Repository: ports >>>>> X-Git-Refname: refs/heads/main >>>>> X-Git-Reftype: branch >>>>> X-Git-Commit: 68df49bce28cc06c143420dce8a925999e5b7456 >>>>> Auto-Submitted: auto-generated >>>> >>>> ^^^^^^^^^^^ >>>> >>>> What's that above? >>> >>> There was a discussion about it on developers@ last week. Guys, can we >>> please stick to 7-bit ASCII for commit messages, at the very least when >>> it does not contain people's names and such? Pretty please. >>> >> >> +1 > > I'm pondering extending the commit check to forbid non us-ascii > characters on the first line. > Please do it. -- Renato Botelho