GitHub code rollback

This day, I wrote a question about code, and I reported an error when I posted my post to the website, saying that system.web.mvc.html lacks references. I knew what happened, so I had to find out the previous Code: in the folder where I want to roll back the code, right-click ==> update to revision ==> and select the corresponding version.

Concept:

Assume that we have many versions with versions 1-10 respectively.

If we select revert to this version here in 7, then operations 8, 9, and 10 after 7 will be eliminated.

If you select revert changes from this version in 7, the modifications to version 7 will be eliminated.

If you select 7, 8 revert changes from this version at the same time, the modifications made in both versions 7 and 8 will be eliminated.

 

Update to revision is similar to revert to revision, which combines uncommitted local modifications. The two of them have the following differences:
Revert to revision will use this Rev as the latest version, but update to revision will not.
Therefore, revert to revision is equivalent to first update to revision, then copy the content to other places, then update, and then overwrite the content. So if you want to recover to a previous version permanently, use revert to revision.
If you want to temporarily recover to a previous version, use update to revision.
Update to revision is much more common than revert to revision.
Check the right-click menu of tortoise SVN. Update to revision is available, but there is no revert to revision.

 

Reference: http://blog.csdn.net/ikscher/article/details/7277015

GitHub code rollback