> From: Rustom Mody <rustompm...@gmail.com> > 1. How did/could those files have been deleted -- as I said I am not a > developer and so have none of my own modifications?
Those files could have been deleted in any way that files can be deleted. Since "git reset --hard" caused them to appear again, it's unlikely that pulling the new commits caused it. My personal guess would be that the new build system doesn't conflicts with files that were generated by the old build system. You say that you did "git pull", followed by a rebuild, but you did not say that you cleaned the build directories before the rebuild. My experience is that when a build system is reorganized, the chances are high that you need to completely clean the build directories to get the new build system to work. > 2. Is reset --hard the correct way? The correct way to do what? If you want a completely clean build environment, "git reset --hard" ensures that all tracked files match the current commit. But you need to do "git status" to see if there are any untracked file in the working directories, and then delete those files. (In your case, there were no such files.) Dale -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
