Yes I supposed last few commits won't be able undo other way. Next time this
will not happen, we will make "safe" commitments first.
What branches were introduced?
The apache branch had master and surefire-954-test only.
The whole problem was with maven-release-plugin:2.2.1 and some other with
SS
I see you have pushed some "interesting" committs to surefire master @
apache. These are a permanent part of history, and cannot be undone.
You also pushed a few "interesting" branches, which I took the liberty
of deleting, sicne they were pointing to existing history.
In general, I find that usin
When you do the git reset --hard command you basically move your local
"master" branch back somewhere else in history. If you make a commit
at the point, you will not be able to push to apache, since it refuses
to rollback history.
To get out of this situation you need to do git merge origin/maste