You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a common issue for Quake mods: some of the files in the repo have Windows-style CRLF line endings, some have Unix/Linux/Mac-style LF line endings, and at least one file has a mixture of the two. This can cause different issues for people on different systems using different tools to work with the files.
A Git repo can be configured so that it stores the files in a normalized format, so that the Git client can automatically convert to or from whatever scheme is appropriate for the user's system (so Windows users get CRLF, and pretty much everyone else gets LF).
HOWEVER, trying to implement this now would almost certainly cause merge conflicts with unmerged branches. The best time to try to address this would be when the code for the next version is finalized and all branches have been merged.
THIS MIGHT HAVE BEEN ADDRESSED?
The text was updated successfully, but these errors were encountered:
From iw on Jan 7, 2020: dumptruckDS/progs_dump_qc#75
This is a common issue for Quake mods: some of the files in the repo have Windows-style CRLF line endings, some have Unix/Linux/Mac-style LF line endings, and at least one file has a mixture of the two. This can cause different issues for people on different systems using different tools to work with the files.
A Git repo can be configured so that it stores the files in a normalized format, so that the Git client can automatically convert to or from whatever scheme is appropriate for the user's system (so Windows users get CRLF, and pretty much everyone else gets LF).
HOWEVER, trying to implement this now would almost certainly cause merge conflicts with unmerged branches. The best time to try to address this would be when the code for the next version is finalized and all branches have been merged.
THIS MIGHT HAVE BEEN ADDRESSED?
The text was updated successfully, but these errors were encountered: