GIT: normalize eol#30
Conversation
|
Given that this change is likely to cause conflicts in other PRs, it should probably be applied after other PRs are merged. |
- Visual Studio project/solution files are always CRLF - all others are auto
324838a to
ad5d8dc
Compare
|
I updated the commit messages to follow the preferred format |
|
@pkoning2 Can you review this, please? Thanks. |
|
@pkoning2 Still waiting on feedback |
|
We're inclined to accept this. Also (a) we need to get this included in updated coding instructions, which we actually need to create to begin with, and (b) it applies to the simh repository also, not just simtools. |
|
I can create a I can also create a basic contributing guidelines for simh as well -- they're basically the same, anyway with minor differences. For simh, I think it should be approached on a file-by-file basis so as not to bung up any pending PRs. Chew on the elephant one bite at a time until done. |
|
@pkoning2 So are we good to merge this PR? |
The files in the repository had a mixture of line endings -- some were LF, some were CR LF.
This PR adds a
.gitattributesthat specifies that Visual Studio project and solution files are explicitly CR LF and the remainder aretext=auto.The EOL for files in the repository are normalized to LF line endings.
When you check out the repository on unix, you get text files with LF line endings.
When you check out the repository on Windows, you get text files with CR LF line endings.
git marshals back and forth when you push/pull from the repository on either platform.