I'll probably push the normalization tonight. The diffstat is: 4638 files changed, 621624 insertions(+), 621624 deletions(-)
We seem to have about 6000 files in total so 1400 remains untouched. It's weird though... I've been following the instructions at https://help.github.com/articles/dealing-with-line-endings#platform-all But the git rm --cached -r .; git reset --hard only updated ~150 files - suspiciously these were the 150 _last_ files of all files taken in alphabetic order. I committed that and repeated and now it updated the next 100 or so files in reverse alphabetical order. Then I tried physically removing all files, I tried the touch command, and repeated it all several times before it stopped finding new files to update. Some git weirdness... /Oskar 2014-08-25 22:05 GMT+02:00 Oskar Berggren <[email protected]>: > We have the .editorconfig in the src directory already. Now if there only > was a way to have VS lock up if the tool isn't installed. :) > > > 2014-08-24 23:27 GMT+02:00 Alexander Zaytsev <[email protected]>: > > I have no objections. >> >> Also probably we need .editorconfig http://editorconfig.org/ >> >> Best Regards, >> Alexander >> >> >> 2014-08-25 9:22 GMT+12:00 Oskar Berggren <[email protected]>: >> >>> I'm getting very tired of dealing with files in the NH repo that happens >>> to have mixed line endings. Or that are in Unix-format (because something >>> eventually makes them mixed-EOL - I think VS handles LF-files decently, but >>> it seems Reshaper will always insert CRLF during refactor or reformat). >>> >>> Over the last couple of years we have a bunch of commits to adjust line >>> endings for individual files. >>> >>> To get out of this situation I want to alter the .gitattributes to turn >>> git's automatic EOL-conversion back on for text files, and normalize the >>> line endings of existing files. According to the github guidelines: >>> https://help.github.com/articles/dealing-with-line-endings#platform-all. >>> >>> >>> The only drawback is there will be a big commit with the normalization. >>> I think it's good to do it now immediately after the release. >>> >>> >>> /Oskar >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "nhibernate-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nhibernate-development" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
