15,049
edits
Troubleshooting of GIT: Difference between revisions
Jump to navigation
Jump to search
m
→Git Shows Files as Modified After chmod — File Mode Changes
| Line 429: | Line 429: | ||
If the output contains only <code>old mode</code> and <code>new mode</code>, without added or removed content lines, the change is caused by the executable bit rather than file contents. | If the output contains only <code>old mode</code> and <code>new mode</code>, without added or removed content lines, the change is caused by the executable bit rather than file contents. | ||
Check the current repository setting with: | Check the current repository setting with: <ref>[https://git-scm.com/docs/git-config?utm_source=chatgpt.com Git - git-config Documentation]</ref> | ||
<pre> | <pre> | ||
| Line 547: | Line 547: | ||
{{exclaim}} Notice: Setting <code>core.fileMode=false</code> does not change the actual operating-system permissions and does not rewrite previously committed file modes. It only tells Git not to treat executable-bit differences in the working tree as modifications. Use a repository-level setting unless the same problem consistently affects all repositories on the machine. | {{exclaim}} Notice: Setting <code>core.fileMode=false</code> does not change the actual operating-system permissions and does not rewrite previously committed file modes. It only tells Git not to treat executable-bit differences in the working tree as modifications. Use a repository-level setting unless the same problem consistently affects all repositories on the machine. | ||
=== Git Submodule Pull Failed: unable to create file — File exists === | === Git Submodule Pull Failed: unable to create file — File exists === | ||