Re: git commit -a reports untracked files after a clone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Philipp Metzler <phil@xxxxxxx> 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.
--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]