git commit -a reports untracked files after a clon

[GoogleCodeExporter]

What steps will reproduce the problem?
1. install git version 1.7.4
2. clone a repo and run "git commit -a"

What is the expected output? What do you see instead?
I would expect: nothing to commit (working directory clean)
Instead it reports: nothing added to commit but untracked files present (use 
"git add" to track)

What version of the product are you using? On what operating system?
1.7.4 on OS X 10.6.7

Please provide any additional information below.
The problem doesn't occur in 1.7.3.5

Starting with git version 1.7.4.4 the command "git status" makes this message 
go away: so if you run the commands in this order the problem goes away:

git clone git@philippmetzler.webmeisterei.com:YOURREPO.git
git commit -a (reports untracked files)
git status
git commit -a (nor untracked files anymore - just because you ran git status 
before)

Original issue reported on code.google.com by goog...@gmail.com on 14 May 2011 at 8:29

[GoogleCodeExporter]

Hi there,

You might report this on #git on irc or on the git mailing list: 
http://dir.gmane.org/gmane.comp.version-control.git

This issue tracker is for the installer itself.

Thanks!

Original comment by timchar...@gmail.com on 14 May 2011 at 8:32

• Changed state: Invalid