Jean-Pierre MartineauandClaude Sonnet 5
f22e8ebdc5
Deploying a file straight to the PicoCalc/Calculinux device (bypassing git, e.g. pscp for a quick on-hardware test) copies the local working tree's line endings as-is. With core.autocrlf=true on Windows that's CRLF, which git on the device then sees as every line "modified" relative to its LF-stored history -- blocking git pull there until the bogus diff is discarded. *.sh already forced eol=lf for the same reason (shebangs/heredocs breaking on CR); *.py gets the same treatment now. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
10 lines
512 B
Plaintext
10 lines
512 B
Plaintext
# Shell scripts run on the Calculinux/Linux target -- keep LF so the shebang and
|
|
# heredoc terminators never pick up a CR that breaks them on the device.
|
|
*.sh text eol=lf
|
|
|
|
# The app itself runs on the same Linux target (see above). Force LF regardless of a
|
|
# contributor's local core.autocrlf, so a file copied straight to the device (bypassing
|
|
# git, e.g. for a quick on-hardware test) never carries CRLF git would otherwise see as
|
|
# a spurious modification blocking the next `git pull` there.
|
|
*.py text eol=lf
|