Hi, the clone command *automatically *detects if your local file system is 'filemode' compatible.
`git help config` search for `core.filemode` " git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary." You may also need to consider how your team works compatibly between OS systems. (what OS/version does the maintainer of the repo being cloned use?) Perhaps give an example of such a "file changed" report. On Wednesday, November 20, 2019 at 1:48:34 PM UTC, Jiří Bělský wrote: > > Hi, > > im pretty sure this must be a bug, no matter what i tried, *git will > always ignore filemode=false in global settings and set filemode=true while > cloning new repositories*, which results in having a lot of files tagged > as changed. > > Commands: > *git config --get --global core.filemode* > returned: *false* > > *git clone [some repository]* > *cd [some repository]* > > *git config --get --local core.filemode* > returned:* true* > > i even tried setting global filemode with sudo, still same result (: > > Elementary OS 5 (based on Ubuntu 18.04) > Git version 2.24.0 (happening on 2.17.X and earlier as well) > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/27ce4968-a05e-4363-8e7f-81c726a332b8%40googlegroups.com.
