Closed naitp closed 7 years ago
Thanks so much! I don't know how that bad byte got in there. However, did you do something that would have committed the file without windows line endings (\r\n)? That appeared to be the case when I pulled the merged file. I just committed a version with the line endings renormalized to Windows line endings.
That byte comes from encoding. If you use UTF instead of ASCII.
What I meant is that none of the other files in that directory have the byte-encoding byte, so I don't know why that file would have it.
Regarding line endings, the only thing I can think of is that the ACE Editor converted them inadvertently when I saved the file (see last comment here: https://github.com/gitlabhq/gitlabhq/issues/3982 from Nov. 2016), but I can't seem to duplicate the issue on any of my repos. Sorry I couldn't be more help with this one. I'll try to duplicate it when I have some more time (when I'm not at work).
No worries! I was just mentioning it because I thought I had put the right magic goo in .gitattributes so that Git would always put in the Windows line endings. I guess line endings and the great tab vs. spaces debate will always be among the great religious battles of the world...
Addresses issue found in https://github.com/Microsoft/ILMerge/issues/1 (Can't compile the code because of Chinese letters).