Miles Bader <miles@xxxxxxx> wrote: > One way to do this seems to be just "git add .", but I'm always slightly > nervous using it because it sits there and churns the disk for an awful > long time (whereas "git status" is instantaneous). Is this the right > thing to do? Is there something funny causing the churning? That's the correct way to add those new files that aren't ignored. The problem is actually a small bug in git-add; we did not take the obvious performance optimization of skipping files that are stat clean in the index. So what is happening here during `git add .` is we are reading and hashing every single file, even if it is already tracked and is not modified. In short we're just working harder than we need to during this operation. I believe this has been fixed in git 1.5.3-rc3 or rc4. Not sure which one; I don't have access to a git repository right now to look it up. -- Shawn. - 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
