{"id":548,"date":"2009-05-18T10:12:03","date_gmt":"2009-05-18T15:12:03","guid":{"rendered":"http:\/\/poojanwagh.opalstacked.com\/poojanblog\/?p=548"},"modified":"2009-06-23T18:47:29","modified_gmt":"2009-06-23T23:47:29","slug":"how-not-to-go-back-in-time-using-git-equivalent-of-svn-revert","status":"publish","type":"post","link":"https:\/\/poojanblog.com\/blog\/2009\/05\/how-not-to-go-back-in-time-using-git-equivalent-of-svn-revert\/","title":{"rendered":"How not to go back in time using git (equivalent of svn revert)"},"content":{"rendered":"

Update: I recovered my lost commit by following the directions here<\/a>. In addition, I had to create a branch from this commit using chekcout -b<\/code>. I then switch to the master<\/code> branch and merged the temporary branch into master<\/code><\/p>\n

It has been written<\/del> posted<\/a> that git revert<\/code> is not the same as svn revert<\/code>. That’s true.<\/p>\n

However, there have been suggestions that the equivalent is git reset --hard <\/code>commit<\/em>. I just did this. It isn’t good. Luckily, I didn’t lose much<\/del>any data. However, doing a --hard<\/code> means that you reset the index<\/em> back in time, too–not just your working copy.<\/p>\n

I’ll admit that I don’t understand git very well. I’m not entirely sure (now that I’ve gone back in time) how to bring myself back to the future.<\/p>\n

Essentially git reset<\/code> means that you want to get rid of changes in your repository: not merely go back in time, see what things looked like, and move forward in time.<\/p>\n

Anyway, a safer thing (for me to have done) would be git checkout <\/code>commit<\/em>.<\/p>\n

The git manual specifically says:<\/p>\n

–hard<\/p>\n

Matches the working tree and index to that of the tree being switched to. Any changes to tracked files in the working tree since commit<\/em> are lost.<\/strong><\/p><\/blockquote>\n

Wonder if I’m too feeble to be MacGyver and need a James Bond<\/a>. On the other hand, now that I’ve learned this lesson, maybe I’m better off sticking here.<\/p>\n","protected":false},"excerpt":{"rendered":"

There have been suggestions that the equivalent is git reset --hard <\/code>commit<\/em>. I just did this. It isn’t good. Luckily, I didn’t lose much data. However, doing a --hard<\/code> means that you reset the index<\/em> back in time, too–not just your working copy.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[4],"tags":[31],"class_list":["post-548","post","type-post","status-publish","format-standard","hentry","category-desktop-computing","tag-git"],"jetpack_featured_media_url":"","jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/posts\/548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/comments?post=548"}],"version-history":[{"count":12,"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/posts\/548\/revisions"}],"predecessor-version":[{"id":600,"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/posts\/548\/revisions\/600"}],"wp:attachment":[{"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/media?parent=548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/categories?post=548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/poojanblog.com\/blog\/wp-json\/wp\/v2\/tags?post=548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}