Cache corruption

TicGit-ng had/has a cache corruption bug, inherited from the original TicGit project.

###Problem After changing the 'ticgit' branch directly using git and not through TicGit-ng, such as if you were to manually merge someone else's ticgit branch into yours, or if you had to perform manual repairs on your ticgit branch to remove a commit for example, the cache/state that TicGit-ng keeps in ~/.ticgit / ~/.ticgit-ng causes the state of TicGit to become corrupt. The state is used before checking to see if state matches the state in git.

###Resolutions After manually editing the ticgit branch and before running any Ticgit commands, delete the ~/.ticgit and ~/.ticgit-ng directories. This is where the cache / state is stored, and will delete it before running ticgit. You may lose some saved settings.

###Fix The state needs to be checked against the git branch to make sure it is up to date before using it. If it is stale, update/delete it.