Hi,
By cloning by Git for z/OS, in SSH protocol, a repository stored in our Bitbucket manager, and created on Windows, I notice the presence of an x0D character at the end of each line of the files encoded in EBCDIC.
Files encoded in ASCII, or more precisely files that are not subject to codepage conversion, do not have this x0D character at the end of the line.
I had to add an explicit "eol=lf" option in the .gitattributes file on the "*" pattern before cloning on USS to work around this problem.
This is not satisfactory, because we use our Git repositories on various platforms, mainly Windows, and also z/OS-USS, and we don't want to force the handling of line endings in the .gitattributes file.
We want each platform to be free to use whatever line endings it wants.
All of our Git installations, Windows or USS, use the core.autocrlf=true configuration. This has the consequence of storing text files in internal format with an CRLF end-of-line sequence.
When fetching to the working directory, the end-of-line sequence must be adapted to the platform: CRLF for Windows, LF for Unix/Linux, nothing (visible) for USS.
The fact that only transcoded files (ASCII to EBCDIC) are affected by this problem leads me to suspect that it is a Git for z/OS specific anomaly that occurs at the time of this transcoding.
Git version: Git 2.26.2-84
------------------------------
Fallai Denis
M
Self Registered
L'ISLE-ADAM FR
------------------------------