git-untracked

I have a repository on a pc with approximate size of 70GB and when I copied it (not clone, just simple copying) to my mac it shows that some files are untracked while they are already tracked. When I added them, they appeared to be duplicated in the repo objects info but not in the working tree of course. So I made a hard reset to the last commit but the files appeared again as untracked. How can I solve this problem? (knowing that the repo on the pc is working well) Don't copy a repository's working directory from computer to computer. Problem Your working directory has checked out files in

I'm new to Git. I wish to know what are tracked and untracked files? I read "Pro Git", but still couldn't quite understand. Can someone explain to me the difference between the two by providing an example? A file is tracked if it is under version control. As a small example, a C++ project would have Makefile main.cpp interface.hpp worker.cpp as source files; you'd put these under version control. During build, main.o worker.o myapp are generated; these do not belong under version control, so you do not use git add on them. They remain untracked , because git does not care what happens to them.

Is it possible to skip the staging area and (also) commit untracked, new files to git in a single built-in, command-line command ? If not, what are the alternatives ? http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository Providing the -a option to the git commit command makes Git automatically stage every file that is already tracked before doing the commit, letting you skip the git add part: $ git commit -a -m 'added new benchmarks' Thanks. Using a single, built-in, command-line command? No. Using two commands: git add -A git commit Using a custom alias: Add this to