git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/2] commit: improve UTF-8 validation

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jun 29, 2013, 17:39 UTC
Message-ID
<20130629173940.GA226907@vauxhall.crustytoothpaste.net>

This series contains a pair of patches that improve the validation of the UTF-8 used in commit messages. Invalid codepoints, such as surrogates and guaranteed non-characters, are rejected, along with overlong UTF-8 sequences.

brian m. carlson (2):
  commit: reject invalid UTF-8 codepoints
  commit: reject overlong UTF-8 sequences
 commit.c                   | 28 +++++++++++++++++++++++++---
 t/t3900-i18n-commit.sh     | 17 +++++++++++++++++
 t/t3900/UTF-8-invalid.txt  |  3 +++
 t/t3900/UTF-8-overlong.txt |  3 +++
 4 files changed, 48 insertions(+), 3 deletions(-)
 create mode 100644 t/t3900/UTF-8-invalid.txt
 create mode 100644 t/t3900/UTF-8-overlong.txt
-- 
1.8.3.1
Message 1 of 1 in “commit: improve UTF-8 validation”
  1. 0/2 commit: improve UTF-8 validationbrian m. carlson, Jun 29, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.