From: Junio C Hamano <gitster@pobox.com>
Date: Sun, 15 May 2011 03:43:32 GMT
Subject: Re: git commit -a reports untracked files after a clone
Message-ID: <7v39kgr5ln.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7B399C74-8048-42BA-8672-9D7964F24888@goli.at>

Philipp Metzler <phil@goli.at> writes:

> This is how you can reproduce the problem:
> 1. clone a repo
> 2. run the command "git commit -a"

Does it reproduce with _any_ repository, or just a particular one?  If it
is the latter, then the above description is useless for anybody to start
formulating any theory on what goes wrong. Sorry.

You being on OS X, I would guess that you may have a pathname in the
project that HFS+ does not like.

On HFS+, when a program creates a file with "open(filename, O_CREAT)",
reading the directory the created path is in with readdir() does not
return the string given when it was created but something else for certain
pathnames; you may be seeing that git is confused by that behaviour.

But that is just a wild guess.