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

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

 



On Mon, May 16, 2011 at 02:38:33PM +0200, Philipp Metzler wrote:

> Could be a race condition / heisenbug yep. The result of "git commit
> -a" differs - the directories vcs-svn and xdiff are there all the time
> but not the others. The only constant thing is that the command "git
> status" always "cleans up" everything. Another run:

OK, I'm making some progress. I can replicate on Linux with:

  $ git config core.ignorecase true
  $ git clone git foo
  $ cd foo && git commit -a

which gives a bunch of directories which contain tracked contents. Doing
"git status" makes the problem go away, but then doing this makes it
come back:

  $ rm .git/index
  $ git read-tree --reset HEAD

And like you, it doesn't trigger with "-uall".

So it is something about:

  1. A fresh index that is perhaps missing stat information for some
     entries.

  2. Stopping the traversal at the directory boundary rather than
     looking at details of each directory ("-uall").

  3. core.ignorecase

But it is definitely repeatable. Which is good, because that will make
it easier to track down. :)

I'll see what I can do, but it may not be today.

-Peff
--
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]