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

[PATCH 1/2] doc/gitattributes: fix typo (UTF-16LE-BOM)

From
Andrew Molyneux <andrew.molyneux@neuxpower.com>
Date
May 3, 2019, 14:09 UTC
Message-ID
<20190503140952.9029-1-andrew.molyneux@neuxpower.com>
Encoding name was erroneously documented as UTF-16-LE-BOM; this should
in fact be UTF-16LE-BOM (no hyphen between '16' and 'LE').
---
 Documentation/gitattributes.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
index 9b41f81c06..bdd11a2ddd 100644
--- a/Documentation/gitattributes.txt
+++ b/Documentation/gitattributes.txt
@@ -346,7 +346,7 @@ automatic line ending conversion based on your platform.
 
 Use the following attributes if your '*.ps1' files are UTF-16 little
 endian encoded without BOM and you want Git to use Windows line endings
-in the working directory (use `UTF-16-LE-BOM` instead of `UTF-16LE` if
+in the working directory (use `UTF-16LE-BOM` instead of `UTF-16LE` if
 you want UTF-16 little endian with BOM).
 Please note, it is highly recommended to
 explicitly define the line endings with `eol` if the `working-tree-encoding`
-- 
2.21.0.windows.1
Next: Andrew Molyneux
Message 1 of 4 in “doc/gitattributes: fix typo (UTF-16LE-BOM)”
  1. 1/2 doc/gitattributes: fix typo (UTF-16LE-BOM)Andrew Molyneux, May 3, 2019
  2. 2/2 tests: fix typo (UTF-16LE-BOM) in test nameAndrew Molyneux, May 3, 2019
  3. Torsten BögershausenMay 3, 2019
  4. Andrew MolyneuxMay 4, 2019

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.