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=

In message <prekcoqe5nfc2fca5udzmbz5m3pjcugw3lotc3uf33wub5ca53@545f2npo4j3d>
, M
athieu Arnold writes:
> 
> --jcsnj57htrhtkdq5
> Content-Type: text/plain; protected-headers=v1; charset=iso-8859-1
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> Subject: Re: git: 68df49bce28c - main - =?utf-8?B?PT91dGYtOD9RP3d3dy9mb3Jn?=
>  =?utf-8?Q?ejo=3A_Updat?= =?utf-8?Q?e?= 7.0.12 =E2=86=92 7.0.13 (fixes
>  security vulnerabiliti=
> MIME-Version: 1.0
>
> Le Mon, Feb 10, 2025 at 03:32:12PM +0100, Fernando Apestegu=EDa a =E9crit :
> > El lun, 10 feb 2025, 15:05, Alexey Dokuchaev <danfe@freebsd.org> escribi=
> =F3:
> >=20
> > > 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)?=3D
> > > > > MIME-Version: 1.0
> > > > > Content-Type: text/plain; charset=3Dutf-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.
> > >
> >=20
> > +1
>
> I'm pondering extending the commit check to forbid non us-ascii
> characters on the first line.

This makes sense as a) the inbox in older mail clients show strange 7-bit 
ASCII subject lines plus depending on one's locale commit logs contain 
various escape and other sequences that may only display correctly in the 
selected locale. i.e.,


update 5.29.1.20241207 <E2><86><92> 5.29.1.20250208

I see this a lot at $JOB where customers send emails which when cut and 
pasted into something like /etc/hosts results in some bizarre behaviour 
after the file is saved.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  https://FreeBSD.org
NTP:           <cy@nwtime.org>    Web:  https://nwtime.org

			e^(i*pi)+1=0