Tracked files become untracked in some obscure scenario
- From
- Stéphane Corlosquet <scorlosquet@gmail.com>
- Date
- Aug 9, 2011, 19:59 UTC
- Message-ID
- <CAGR+nnFM+Pr29h4POarx5rQdrTuMvtwwZLwVPZuChSDKQjLg4g@mail.gmail.com>
Hi,
I'm encountering a very strange bug where some directory containing one file becomes untracked when it should be tracked. I originally found this bug in a bigger repository, but I isolated the culprit files into a small tarball which you can download from http://files.openspring.net/tmp/gitbug-20110809.tgz
This bug occurs on the following three configs: Mac OS X Snow Leopard with git 1.7.4.1 Mac OS X Snow Leopard with git 1.7.5 Mac OS X Lion with git 1.7.4.4 I could not reproduce on Ubuntu.
To reproduce, extract the tarball and try to add its content into a fresh repo: $ git init Initialized empty Git repository in /private/tmp/stemtest/.git/ $ git add . $ git status # On branch master # # Initial commit # # Changes to be committed: # (use "git rm --cached <file>..." to unstage) # # new file: drupal/sites/all/modules/scf/pubnode_docbook4/xsl/docbook-xsl-1.73.2/common/olink.xsl # new file: files/pubnode/ab4d8c648ef8e26312beaba802a503d1f8081bb6/README # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # files/pubnode/ab4d8c648ef8e26312beaba802a503d1f8081bb6/
From there onwards, if I commit and do other operations, this directory will remain in the untracked files list. I'm terribly confused by this bug. It seems it has to do with the paths of both files, since if I rename them, the bug does not happen. But I can't explain what's going on.
regards, Steph.