Add .gitattributes: force LF line-endings for deterministic baseline #5
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "add-gitattributes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
There is no
.gitattributes, so checkout line-endings depend on the buildhost's
core.autocrlf. On tanis this yields CRLF, which just broke therecovery:
build-baseline.shdied with/usr/bin/env: 'bash\r', and aCRLF build tree would push the whole baseline back out of byte-sync with the
docroot (re-triggering the CRLF false-positive storm we just cleaned up).
Fix
* text=auto eol=lf— the source-of-truth LF is authoritative on checkout,regardless of client
core.autocrlf. Binary assets are pinnedbinarysogit never converts them (byte-exact).
Note on submodules
This covers the top-level repo. The
maintenance/common_cadline_librariessubmodules are separate repos — for full determinism either add the same
.gitattributesthere, or setcore.autocrlf=falseon the build host. Thebaseline.slsbuild runs on the host, so a host-levelcore.autocrlf=falseis the pragmatic belt-and-suspenders until the submodules also carry it.
Root incident + post-mortem: illusion3-salt#895.