Dear GetComponents users
[The warning below concerns only the development version of the Einstein Toolkit from the past 24 hours.]
Yesterday, I corrected a problem in GetComponents that would make it sometimes report errors about git repositories when, in fact, everything was fine: In general, to update a git repository that contains local, uncommitted changes, one first "stashes" these changes away, then updates the repository and resolves conflicts, and then "pops" the stashed changes again and resolves conflicts, if necessary. GetComponents would sometimes try to pop local changes when, in fact, there were none.
In the process of correcting this, I introduced (and then corrected) another error. This would result in stashing local changes that were then never popped. Unless you are familiar with git, you may not realise that you now have stashed changes that need popping.
In short: If you used a GetComponents checkout from the past 24 hours on git repositories with local changes, please check for stashed changes named "GetComponents-tmp". To do so, go to the respective repository, and then type "git stash list". To pop a stash manually, type "git stash help" and "git stash pop".
-erik