From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Arsen Arsenović" <arsen@aarsen.me>,
"Emacs Development" <Emacs-devel@gnu.org>
Subject: Re: miscue in latest commit of Arsen Arsenović patch
Date: Tue, 24 Dec 2024 13:55:08 +0000 [thread overview]
Message-ID: <Z2q9PBkpCuOGTisA@MAC.fritz.box> (raw)
In-Reply-To: <239903b8-061e-4257-bd47-875a7ae54cec@cs.ucla.edu>
Hello, Paul.
On Mon, Dec 23, 2024 at 13:47:31 -0800, Paul Eggert wrote:
> The recent Emacs commit 39380e1bd3bfc26e355445590e243fcfa940fc9f should
> look like this in 'git log' output:
> commit 39380e1bd3bfc26e355445590e243fcfa940fc9f
> Author: Arsen Arsenović <arsen@aarsen.me>
> AuthorDate: Sun Dec 22 19:33:29 2024 +0000
> Commit: Alan Mackenzie <acm@muc.de>
> CommitDate: Sun Dec 22 19:33:29 2024 +0000
> Java Mode: introduce the keyword `assert'.
> ...
> However, there was a glitch and instead I see a blotch "�" (U+FFFD
> REPLACEMENT CHARACTER) where there should be "ć" (U+0107 LATIN SMALL
> LETTER C WITH ACUTE).
> Since Arsen has another patch committed (by Dmitry) without the glitch,
> I expect the problem is on Alan's end. Alan, are you running Emacs in a
> single-byte locale to commit patches?
I'm running in a UTF-8 locale. I don't know yet exactly what I did
wrong, but I'll be more careful in the future.
> If so, I suggest using a UTF-8 locale instead, whenever the commit
> contains non-ASCII characters in the author's name or commit message.
> To help avoid similar glitches in the future I installed the attached.
An excellent idea!
> Apologies to Arsen for the misspelling.
Apologies from me, too.
Plus regret that git was designed to prevent typos in commit messages
from being corrected.
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2024-12-24 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 21:47 miscue in latest commit of Arsen Arsenović patch Paul Eggert
2024-12-24 0:16 ` Stefan Kangas
2024-12-24 13:55 ` Alan Mackenzie [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z2q9PBkpCuOGTisA@MAC.fritz.box \
--to=acm@muc.de \
--cc=Emacs-devel@gnu.org \
--cc=arsen@aarsen.me \
--cc=eggert@cs.ucla.edu \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).