4 ms·
>it's not "rewriting history" because you've always got reflog and cryptographically secure version hashes To avoid having to go to the reflog, you can follow
by aaronblohowiak 14y ago
>it's not "rewriting history" because you've always got reflog and cryptographically secure version hashes
To avoid having to go to the reflog, you can follow this simple procedure: branch before rebase. Then when you're comfortable, just change the branch to point at the new ref. This is the rename(2) approach to rebasing :D
- snprbob86 14y ago> To avoid having to go to the reflog Why should I avoid having to go to the reflog? I've met a few folks that, upon learning about reflog, think that every time they run `git reflog` they are admitting that they made a mistake or have otherwise failed to accomplish some task with Git. It's not a failure to need reflog; even if it was, you shouldn't have such an aversion to failure. I frequently run reflog to re-orient myself just like I do with `git log` or `git status`.
- aaronblohowiak 14y agoInteresting point, I will try to take this attitude and approach and see how I like it.