From: Russell, Scott <scott.russell2@ncr.com>
Date: Mon, 16 Aug 2021 18:53:14 GMT
Subject: RE: git clone corrupts file.
Message-ID: <BN6PR15MB14268392DBC2F0C210EBE803CBFD9@BN6PR15MB1426.namprd15.prod.outlook.com>
In-Reply-To: <YRqzmC5ubd0TEWL/@coredump.intra.peff.net>

Okay, thanks.  I will look for that.  


Thanks, 

Scott Russell
Staff SW Engineer 
NCR Corporation 
Phone: +17706237512
Scott.Russell2@ncr.com  |  ncr.com
       

-----Original Message-----
From: Jeff King <peff@peff.net> 
Sent: Monday, August 16, 2021 2:51 PM
To: Russell, Scott <Scott.Russell2@ncr.com>
Cc: brian m. carlson <sandals@crustytoothpaste.net>; git@vger.kernel.org
Subject: Re: git clone corrupts file.

*External Message* - Use caution before opening links or attachments

On Mon, Aug 16, 2021 at 12:53:36PM -0400, Jeff King wrote:

> But an alternative workflow, if you really want UTF-16 in the working 
> tree, is to convert between UTF-8 and UTF-16 as the files go in and 
> out o the working tree. There's no built-in support for that, but you 
> could do it with a custom clean/smudge filter. That would let Git 
> store UTF-8 internally, do diffs, etc.

Oh, by the way, I totally forgot that we added an internal version of this, which is easier to configure and much more efficient. See the "working-tree-encoding" attribute in "git help attributes".

Just in case you do want to go that route.

-Peff