Windows line-ending can potentially cause havoc when importing into Perforce #970
yangskyboxlabs
started this conversation in
General
Replies: 2 comments
-
Thank you for bringing this up and for opening #969. While using |
Beta Was this translation helpful? Give feedback.
0 replies
-
@yangskyboxlabs Line-ending issues should be resolved in #986. We've also added automation checks to help prevent them from reappearing in the future. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I don't think this is a bug-worthy issue per se, but is annoying enough that I wanted to raise some awareness of it.
There are some source files in the repo that use
CRLF
line ending, whilst the majority areLF
. When the former is submitted into Perforce from a workspace that usesLineEnd: unix
, p4 will preserve theCR
on server (the intended behaviour is to normalize toLF
for storage). These line endings will then materialize asCRCRLF
in a Windows workspace, and Unreal will be very unhappy about it:Something to keep in mind for new sources that are added. I imagine dumping a source package into p4 is a very common scenario, although very, very rarely with a workspace configured for
unix
line ending.Beta Was this translation helpful? Give feedback.
All reactions