I would be grateful for any thoughts about the follow problem.
Git status reports untracked files:
$ git status
# On branch master
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# resource.enlighten/map/enlighten_test/.enlighten/__build_object__/geometry/land_9/processed/
nothing added to commit but untracked files present (use "git add" to track)
But we have files at this directory at index:
$ git ls-tree -r HEAD |grep land_9/processed/root.pim
100644 blob 9eeca5c75dc2c945600b6e0d253a8cb8191b7e80
resource.enlighten/map/enlighten_test/.enlighten/__build_object__/geometry/land_9/processed/root.pim
I have checked this error appear after the first commit, that added this file.
I have tried:
1. Clone repo.
2. Clean/Checkout file (as described at this [1] article) - after
checkout status is untracked.
3. Copy full directory resource.enlighten/ to another repo and add
commit - no errors.
4. Run git fsck - no errors.
Git version 1.8.1.2. for Windows
Git config:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
compression = 1
Thank you in advance.
[1] http://stackoverflow.com/questions/11525358/git-untracked-files-list-is-wrong
On Wed, May 29, 2013 at 11:40:56AM +0300, Andrey Kiyanovsky wrote:
Git version 1.8.1.2. for Windows
Git config:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
compression = 1
In the past there have been some problems with status listings of
untracked files when core.ignorecase is in use. I fixed some cases with
a commit that went into v1.7.8, but some problems remained. Karsten
Blees (cc'd) did some work that went into git v1.8.1.6, but I do not
know off-hand if it would fix your case or not.
Can you try with a more recent version of git?
-Peff
I have tried Git 1.8.3 for Windows. Case is fixed. Thank you very much!
2013/6/4 Jeff King [off-list ref]:
On Wed, May 29, 2013 at 11:40:56AM +0300, Andrey Kiyanovsky wrote:
quoted
Git version 1.8.1.2. for Windows
Git config:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
compression = 1
In the past there have been some problems with status listings of
untracked files when core.ignorecase is in use. I fixed some cases with
a commit that went into v1.7.8, but some problems remained. Karsten
Blees (cc'd) did some work that went into git v1.8.1.6, but I do not
know off-hand if it would fix your case or not.
Can you try with a more recent version of git?
-Peff
Am 04.06.2013 11:05, schrieb Andrey Kiyanovsky:
I have tried Git 1.8.3 for Windows. Case is fixed. Thank you very much!
2013/6/4 Jeff King [off-list ref]:
quoted
On Wed, May 29, 2013 at 11:40:56AM +0300, Andrey Kiyanovsky wrote:
quoted
Git version 1.8.1.2. for Windows
Git config:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
compression = 1
In the past there have been some problems with status listings of
untracked files when core.ignorecase is in use. I fixed some cases with
a commit that went into v1.7.8, but some problems remained. Karsten
Blees (cc'd) did some work that went into git v1.8.1.6, but I do not
know off-hand if it would fix your case or not.
Yep, the hash collision bug can definitely cause this with ignorecase=true, glad it helped.
Another case in which Git for Windows will report tracked files as untracked is if you upgrade from < 1.7.10 with non-ASCII file names in the repository. Particularly annoying are hyphens (\u00ad), which look just like ASCII minus (\u002d). See [1] for details.
[1] https://github.com/msysgit/msysgit/wiki/Git-for-Windows-Unicode-Support