Re: Changing encoding of a file : What should happen to CRLF in file ?
- From
Torsten Bögershausen <tboegi@web.de>
- Date
- Nov 16, 2017, 16:15 UTC
- Message-ID
- <20171116161506.GA20809@tor.lan>
- In-Reply-To
- <CAJ_+vJ7am7dU9B0qTYVtxpkHoZdV45ciZN5ifbv9W8xRO2o=EQ@mail.gmail.com>
On Thu, Nov 16, 2017 at 12:35:33AM +0530, Ashish Negi wrote:
Show 15 quoted lines
> On windows : > > git --version > git version 2.14.2.windows.2 > > On linux : > > git --version > git version 2.7.4 > > I would like to understand the solution : > If i understood it correctly : it removes file_name.txt from index, so > git forgets about it. > we then add the file again after changing encoding. This time, git > takes it as utf-8 file and converts crlf to lf when storing it > internally. > Right ?
Yes, exactly. (In a coming release of Git there will be a "git add --renormalize <pathspec>" )
> > Thank you for the support. >
Thanks for a clean bug report. Actually it is a bug, I put it on my to do list