git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug - Dirty submodule differences between OSX/Ubuntu

From
Stefan Beller <sbeller@google.com>
Date
Jul 11, 2017, 00:05 UTC
Message-ID
<CAGZ79kYNL7-TPkn2F_i3g5kO4C+1VeZh8ERigA4LTqck1ktLzw@mail.gmail.com>
In-Reply-To
<20170710235321.m3xfx2lfsvyirzme@genre.crustytoothpaste.net>

On Mon, Jul 10, 2017 at 4:53 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 30 quoted lines
> 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?)

Previous: brian m. carlson
Message 3 of 3 in “Bug - Dirty submodule differences between OSX/Ubuntu”
  1. Steve KallestadJul 9, 2017
  2. brian m. carlsonJul 10, 2017
  3. Stefan BellerJul 11, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.