On Mon, Jul 10, 2017 at 4:53 PM, brian m. carlson <sandals@xxxxxxxxxxxxxxxxxxxx> wrote: > On Sun, Jul 09, 2017 at 01:42:47PM -0700, Steve Kallestad wrote: >> change into the submodule directory and run status >> cd python-mode.el >> git status >> >> On ubuntu: >> On branch master >> Your branch is up-to-date with 'origin/master'. >> nothing to commit, working directory clean >> >> On OSX: >> On branch master >> Your branch is up-to-date with 'origin/master'. >> Changes not staged for commit: >> (use "git add/rm <file>..." to update what will be committed) >> (use "git checkout -- <file>..." to discard changes in working directory) >> >> deleted: EXTENSIONS >> >> no changes added to commit (use "git add" and/or "git commit -a") > > This is an artifact of using a case-insensitive file system. There is a > directory called "extensions" and so git has not checked out the file > "EXTENSIONS", as there's already a file system object. It therefore > sees it as deleted, since git tracks only files (and not really > directories, but trees of files). > > This repository is always going to show as modified on a > case-insensitive file system. You can either ask the maintainers to > change it, or reformat your disk with a case-sensitive file system. While this is certainly not the answer Steve hoped for, we should see if there are any implications by the user of submodules, i.e. is this behavior reproducable without submodules? (In case it is not, do we want to have the same checks in place for gitlinks as for directories?)
