Skip to content

Run git renormalize#5997

Merged
nickva merged 1 commit into
3.5.xfrom
cherry-pick-git-attributes-renormalize
May 11, 2026
Merged

Run git renormalize#5997
nickva merged 1 commit into
3.5.xfrom
cherry-pick-git-attributes-renormalize

Conversation

@nickva
Copy link
Copy Markdown
Contributor

@nickva nickva commented May 11, 2026

(Cherry-pick from main for 3.5.x git cherry-pick 0a50108)

This should fix gradlew.bat being show as modified even after a fresh git clone:

modified:   extra/nouveau/gradlew.bat

That makes the dist tarball as "dirty" so it breaks our releases.

This seems to happen because extra/nouveau/gradlew.bat was stored with cr/lf endings in git, but then we also modified .gitattributes to have text eol=crlf, which indicates we want to store the file with lf and only apply cr/lf after the checkout on Windows. So managed to thoroughly confuse git with that we wanted to do.

It turns out we can fix this with git add --renormalize . so that's what this commit does [1].

[1] https://stackoverflow.com/questions/7156694/git-how-to-renormalize-line-endings-in-all-files-in-all-revisions

This should fix `gradlew.bat` being show as `modified` even after a fresh
git clone:

```
modified:   extra/nouveau/gradlew.bat
```

That makes the dist tarball as "dirty" so it breaks our releases.

This seems to happen because `extra/nouveau/gradlew.bat` was stored with cr/lf
endings in git, but then we also modified `.gitattributes` to have `text
eol=crlf`, which indicates we want to store the file with `lf` and only apply
`cr/lf` after the checkout on Windows. So managed to thoroughly confuse git
with that we wanted to do.

It turns out we can fix this with `git add --renormalize .` so that's what this
commit does [1].

[1]
https://stackoverflow.com/questions/7156694/git-how-to-renormalize-line-endings-in-all-files-in-all-revisions
@nickva nickva merged commit 5b4d921 into 3.5.x May 11, 2026
1 check was pending
@nickva nickva deleted the cherry-pick-git-attributes-renormalize branch May 11, 2026 04:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant