develooper Front page | perl.perl5.porters | Postings from June 2019

Re: [perl #134180] [PATCH] overload::OverloadedStringify docs andtests

Thread Previous | Thread Next
June 6, 2019 15:41
Re: [perl #134180] [PATCH] overload::OverloadedStringify docs andtests
Message ID:
"Hugo van der Sanden via RT" <> writes:

> A minor comment: not sure if we have a policy on it, but for me there
> should be a preference to have commit messages ASCII where possible.

Why?  This is 2019, everything should be Unicode-capable by now, and
we've indeed been using non-ASCII characters in commit messages for a
long time.

~/src/perl$ git log -P --grep='[^[:ascii:]]' --oneline |wc -l

The earliest non-ASCII commit message is:

    commit f31700dc8965c83194d956522e573c5d4fdb4611
    Author: Gurusamy Sarathy <>
    Date:   1998-08-07 21:36:04 +0000

        don't use © in (suggested by M.J.T. Guy)

        p4raw-id: //depot/maint-5.005/perl@1749

> All three of your commit messages have some utf8 in there, and in no
> case does it look particularly necessary.

A lot of the non-ASCII in our commit history not "particularly
necessary": stuff like curly quotes (both from compiler messages and
manually typed), bullets, and ellipses.

- ilmari
"I use RMS as a guide in the same way that a boat captain would use
 a lighthouse.  It's good to know where it is, but you generally
 don't want to find yourself in the same spot." - Tollef Fog Heen

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About