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 using "gitk --all" is a very good tool to try to understand what's going on when I'm confused. K 2014-12-24 11:41 GMT+01:00 Kristian Rosenvold <kristian.rosenv...@gmail.com>: > 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/master > before pushing (assuming git-wip-us.apache.org is origin) > > Kristian > > > 2014-12-24 1:49 GMT+01:00 <tibo...@lycos.com>: >> I need a help with reseting the master >> git-wip-us.apache.org/repos/asf/surefire. >> I did like this: >> git reset --hard f7558cb8ff087d5aaf114ec291babac31896bef3 >> git commit >> git push -u https://git-wip-us.apache.org/repos/asf/maven-surefire.git >> master >> GitHub is telling me: >> remote: Rewinding refs/heads/master is forbidden. >> Is there another way to reset the HEAD to another hash? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
