From: Tim Landscheidt <tim@tim-landscheidt.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: UTF-8 characters in commit messages (was: [PATCH] ; Simplify (with-current-buffer (get-buffer …) …))
Date: Fri, 15 Mar 2024 09:16:34 +0000 [thread overview]
Message-ID: <87a5mzkg7h.fsf_-_@vagabond.tim-landscheidt.de> (raw)
In-Reply-To: <86sf0t9js8.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 14 Mar 2024 12:42:31 +0200")
Eli Zaretskii <eliz@gnu.org> wrote:
> […]
> For the future, please avoid using non-ASCII characters in commit log
> messages.
I had only looked at CONTRIBUTE's:
| - Commit messages should contain only printable UTF-8 characters.
Further down, the test commit-msg performs is described as:
| - commit log message should include only valid printable ASCII and
| UTF-8 characters;
The GNU Coding Standards are a bit more explicit about this:
| Sticking to the ASCII character set (plain text, 7-bit
| characters) is preferred in GNU source code comments, text
| documents, and other contexts, unless there is good reason
| to do something else because of the application domain. For
| example, if source code deals with the French Revolutionary
| calendar, it is OK if its literal strings contain accented
| characters in month names like “Floréal”. Also, it is OK
| (but not required) to use non-ASCII characters to represent
| proper names of contributors in change logs (see Change
| Logs).
Perhaps the first line quoted above could be rephrased à la:
| - Commit messages should contain only valid printable ASCII
| characters. If necessary, they may contain printable
| UTF-8 characters.
Tim
next prev parent reply other threads:[~2024-03-15 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 0:21 [PATCH] ; Simplify (with-current-buffer (get-buffer …) …) Tim Landscheidt
2024-03-14 10:42 ` Eli Zaretskii
2024-03-15 9:16 ` Tim Landscheidt [this message]
2024-03-15 11:32 ` UTF-8 characters in commit messages (was: [PATCH] ; Simplify (with-current-buffer (get-buffer …) …)) Eli Zaretskii
2024-03-15 12:43 ` UTF-8 characters in commit messages Tim Landscheidt
2024-03-19 2:02 ` Richard Stallman
2024-03-19 2:26 ` Collin Funk
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=87a5mzkg7h.fsf_-_@vagabond.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.