Re: Bug - Dirty submodule differences between OSX/Ubuntu

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Jul 10, 2017, 23:53 UTC
Message-ID: <20170710235321.m3xfx2lfsvyirzme@genre.crustytoothpaste.net>
In-Reply-To: <CALs7=Px4nqr6LhOTEQY80WbahRRuaKut-Us5tP7Puda0kb5EdQ@mail.gmail.com>

On Sun, Jul 09, 2017 at 01:42:47PM -0700, Steve Kallestad wrote:

Show 19 quoted lines

> 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.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204