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

[Jeff King <peff@peff.net>]

On Mon, May 16, 2011 at 12:49:07PM +0200, Philipp Metzler wrote:

> [phil@Silberpfeil git]$ git commit -uall
> # On branch master
> nothing to commit (working directory clean)

Hmm, nothing. That's odd.

> [phil@Silberpfeil git]$ git commit -a
> # On branch master
> # Untracked files:
> #   (use "git add <file>..." to include in what will be committed)
> #
> #	t/t9154/
> #	t/t9601/
> #	t/t9602/
> #	t/t9603/
> #	t/t9700/
> #	t/valgrind/
> #	templates/
> #	vcs-svn/
> #	xdiff/
> nothing added to commit but untracked files present (use "git add" to track)

And now totally different output from before, and from the previous run.

So this is really strange. The fact that the list of directories is
_different_ from your previous posting implies to me that it is not
something about those particular files, but rather some weird race
condition in the creation of those directories or the index.

But then the fact that we see them with no "-u", but don't see them with
"-uall" implies some weird heisenbug in git's directory traversal. What
happens if you do "git commit --all -uall"? I'd like to see if the thing
that switches the behavior is the presence of "--all" or the absence of
a "-u" option.

-Peff