I\'ve been tasked with giving a presentation on Git to my colleagues, who are almost entirely Windows users who are used to using TortoiseCVS. I\'ve been using Git for about
The truth is even worse than the answers so far have let on. I tried an experiment: git add some changes to the index, restore the working tree to match the current HEAD, and run a TortoiseGit commit.
It listed the changed file as one of the files eligible to be included in the commit, so it was aware something was changed, which gives the impression that at least it knows how to finish a commit that's already been staged by another tool. But when I chose it the commit actually used the working tree copy and destroyed the uncommitted data in the index and the commit ended up being a no-op on that file.
A dangerous tool, I think I'll be avoiding it.