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

Re: RFC: Native clean/smudge filter for UTF-16 files

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 25, 2017, 02:32 UTC
Message-ID
<xmqqy3mvks0v.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20171124180401.GB29190@sigill>
Jeff King <peff@peff.net> writes:
> So anyway, that is an alternate strategy, but I think I like "canonical
> in-repo text is utf-8" approach a lot more, since then git operations
> work consistently. There are still a few rough edges (e.g., I'm not sure
Sounds like a good way forward.
> if you could apply a utf-8 patch directly to a utf-16 working tree file.
> Certainly not using "patch", but I'm not sure how well "git apply" would
> handle that case either). But I think it would mostly Just Work as long
> as people were willing to set their encoding attributes.

It should work (or fail) just like applying LF patch to CRLF working tree, so I wouldn't worry too much about it.

Thanks.
Previous: Jeff KingNext: Lars Schneider
Message 4 of 6 in “RFC: Native clean/smudge filter for UTF-16 files”
  1. Lars SchneiderNov 23, 2017
  2. Torsten BögershausenNov 23, 2017
  3. Jeff KingNov 24, 2017
  4. Junio C HamanoNov 25, 2017
  5. Lars SchneiderDec 3, 2017
  6. Jeff KingDec 4, 2017

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.