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

Re: [BUG] git status doesn't handle submodules properly on OSX

From
Lars Hoss <lars@woeye.net>
Date
Oct 16, 2008, 11:23 UTC
Message-ID
<3520b7a9009f072cfc3aeb82ae205e6b.squirrel@webmail.highteq.net>
In-Reply-To
<524C98C8-C3A5-4501-932A-2F0ACDE2886A@simplicidade.org>
Update:

Ok, I compiled several git versions from the git repo with the following results:

v1.5.6.5 works v1.6.0.2 fails v1.6.0 fails v1.6.0-rc0 fails

Given a git repo with a submodule 1.5.6.5 works (no untracked files) but the same repo fails with 1.6.0-rc0 (lists submodule folders under untracked files).

So something between 1.5.6.5 and 1.6.0-rc0 broke it for me. A quick diff between the two version revealed a lot of changes. Thus tracking down the issue might not be easy for someone who is not involved in the code.

Maybe someone can give me a hint where to look? For example where does "git status" decide whether a given filesystem folder should be ignored with regard to .gitmodules?

Yours, Lars

Show 59 quoted lines
>
> On Oct 15, 2008, at 3:51 PM, Lars Hoss wrote:
>
>>> Works for me on Leopard
>>>
>>> Vienna:a pieter$ git submodule add ~/projects/GitX/ gitx
>>> Initialized empty Git repository in /Users/pieter/a/gitx/.git/
>>> Vienna:a pieter$ git st
>>> # On branch master
>>> # Changes to be committed:
>>> #   (use "git reset HEAD <file>..." to unstage)
>>> #
>>> #	new file:   .gitmodules
>>> #	new file:   gitx
>>> #
>>> Vienna:a pieter$ git --version
>>> git version 1.6.0.2.415.gf9137
>>
>> My git version "1.6.0.2" says:
>>
>> # On branch master
>> # Changes to be committed:
>> #   (use "git reset HEAD <file>..." to unstage)
>> #
>> #	new file:   .gitmodules
>> #	new file:   lib
>> #
>> # Untracked files:
>> #   (use "git add <file>..." to include in what will be committed)
>> #
>> #	lib/
>> git --version
>> git version 1.6.0.2
>>
>> Git was build from macports.
>
> hmms.. Really, I know about fink and Macports and all others, but I'm
> using Mac OS X since version 10.1 (when compiling OSS software was
> near impossible due to Apple decisions) and I've always had better
> results with compiling my own than using any of those OSS repositories.
>
> I understand the appeal, it seems easier, but I would recommend that
> you compile yourself the software packages you depend on.
>
> Regarding git, I saw a git-build.sh script floating around. If you
> cannot find it, you might want to try my own recipe
> (http://tinyurl.com/4ayze6
> ). I compile git master every day (cron) and thats the one I use on my
> main machine.
>
> Best regards,
> --
> Pedro Melo
> Blog: http://www.simplicidade.org/notes/
> XMPP ID: melo@simplicidade.org
> Use XMPP!
>
>
>
Previous: Lars HossNext: Johannes Sixt
Message 13 of 21 in “[BUG] git status doesn't handle submodules properly on OSX”
  1. Lars HossOct 15, 2008
  2. Jeff KingOct 15, 2008
  3. Lars HossOct 15, 2008
  4. Pieter de BieOct 15, 2008
  5. Lars HossOct 15, 2008
  6. Pieter de BieOct 15, 2008
  7. Lars HossOct 15, 2008
  8. Richard BubelOct 15, 2008
  9. Lars HossOct 15, 2008
  10. Pedro MeloOct 16, 2008
  11. Pedro MeloOct 16, 2008
  12. Lars HossOct 16, 2008
  13. Lars HossOct 16, 2008
  14. Johannes SixtOct 16, 2008
  15. Lars HossOct 16, 2008
  16. Lars HossOct 16, 2008
  17. Jeff KingOct 16, 2008
  18. refactor handling of "other" files in ls-files and statusJeff King, Oct 16, 2008
  19. Jeff KingOct 16, 2008
  20. Junio C HamanoOct 17, 2008
  21. Pedro MeloOct 16, 2008

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.