Torsten Bögershausen <tboegi@xxxxxx> writes: >>> What does >>> git diff >>> say ? >> >> Great question. For all the unexpected files it says the >> same thing: >> >> old mode 100755 >> new mode 100644 > > So the solution is to run > git config core.filemode false Thanks for asking a great question. I somehow expected that we probe in init-db.c::create_default_files() for this when we probe for case sensitivity, symlinks, etc., but apparently we don't. I guess we don't because on some filesystems we can't. IIRC, it goes something like: chmod immediately followed by lstat pretends that change to the executable bit stuck, until the in-core buffer at the vfs layer is flushed to the disk platter that holds the filesystem without any notion of executable bit. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html