Re: [PATCH/RFC v1 1/1] Support working-tree-encoding "UTF-16LE-BOM"

Hello again. I appreciate the grown interest in this issue. Torsten, may I know what is the benefit on your code? My PR solved it by only tweaking the utf8.c's function 'has_prohibited_utf_bom', which is likely the shortest way: https://github.com/git/git/pull/550/files In order to make sure ev

Re: git-rebase is ignoring working-tree-encoding

ring to a link which is present in the ut8.h file. El mar., 6 nov. 2018 a las 21:16, Torsten Bögershausen () escribió: > > On Mon, Nov 05, 2018 at 07:10:14PM +0100, Torsten Bögershausen wrote: > > On Mon, Nov 05, 2018 at 05:24:39AM +0100, Adrián Gimeno Balaguer wrote: > > > > []

Re: git-rebase is ignoring working-tree-encoding

El dom., 4 nov. 2018 a las 18:07, Torsten Bögershausen () escribió: > > Thanks for the report. > I have tried to follow the problem from your verbal descriptions > (and the PR) but I need to admit that I don't fully understand the > problem (yet). I have created a PR in the Git's repository. You c

Re: git-rebase is ignoring working-tree-encoding

El dom., 4 nov. 2018 a las 16:48, brian m. carlson () escribió: > Do things work for you if you write this as "UTF-16LE"? When you use > working-tree-encoding, the file is stored internally as UTF-8, but it's > serialized to the specified encoding when written out. When I use UTF-16LE or UTF-16BE

git-rebase is ignoring working-tree-encoding

I’m attempting to perform fixups via git-rebase of UTF-16 LE files (the project I’m working on requires that exact encoding on certain files). When the rebase is complete, Git changes that file’s encoding to UTF-16 BE. I have been using the newer working-tree-encoding attribute in .gitattributes. I