Agreed, EGit is not ready for public consumption. Sticking with Tortoise or command line is the only way to make sure you don't end up doing serious damage to your repos.
Their biggest problem is their treatment of previous changes and parents. It fubars the system by repeatedly introduce previous additions or deletions from your codebase.
I mainly look to egit to help me stage refactorings correctly as move + edit operations in the index. Should I be worried about that?
Have you looked at using "git gui" instead? It seems to be a more stable, reliable, and supported tool than egit. It lacks direct Eclipse integration of course, but in practice I've never found that to be a problem.
how does that address eclipse refactorings?
Maybe I was misunderstanding, but I assumed the parent comment was wanting to be able to easily select individual changes from his re-factoring for committing. Git GUI is great for that. I'm not aware of any additional "refactoring" related functionality that eGit offers above and beyond that.
not had a problem with EGIT once..
Better to just stick with command line + git gui?
Thats what I do (tower for the GUI). The mercurial plugin on the other hand is great.
Been using EGit since it came out without a problem. It's hard for me to live without the in-IDE historical diffs.