Am 25.01.2010 um 12:43 schrieb Michael Ludwig: > Reading up about core.fileMode in git-config(1), I think you've pointed > me to the solution. I should probably just set it to false. If that doesn't > solve the issue, I'll report back. Back with more info: git version 1.6.4.2 Before adding any core.filemode setting to ~/.gitconfig or .git/config: michael@wladimir:/cygdrive/m/REPOS6.TECH.git/comp :-) git config -l user.name=Michael Ludwig user.email=... core.repositoryformatversion=0 core.filemode=true <= filemode already present core.bare=false core.logallrefupdates=true core.ignorecase=true core.autocrlf=false svn-remote.svn.ignore-paths=^(some|paths) svn-remote.svn.url=svn://localhost svn-remote.svn.fetch=:refs/remotes/git-svn svn.authorsfile=authors.txt My git status output after cd to subdir shows many files "modified". But they aren't! Edited ~/.gitconfig to include core.filemode = true [sic]. Here's the diff for the git config output: --- /home/michael/a 2010-01-25 20:36:53.140625000 +0100 +++ /home/michael/b 2010-01-25 20:37:01.421875000 +0100 @@ -4,6 +4,7 @@ alias.ci=checkin alias.co=checkout alias.br=branch +core.filemode=true core.repositoryformatversion=0 core.filemode=true core.bare=false We're seeing core.filemode appear *twice*. Why that? michael@wladimir:/cygdrive/m/REPOS6.TECH.git/comp :-) git st # On branch master nothing to commit (working directory clean) So it seems adding core.filemode = true has fixed the issue, or at least covered the symptoms. Adding core.filemode = false did not cause the phantom modifications to disappear. Note that from reading git-config(1), I had rather assumed this latter setting to have the desired effect. And something seems to be wrong here. Why are modifications flagged when doing git status from a subdir but not from the topdir? -- Michael.Ludwig (#) XING.com -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html