4 ms·
I really like this article but there is a problem with it: what happens if I use one of your techniques and I screw up? These steps you describe are a black box
by edem 10y ago
I really like this article but there is a problem with it: what happens if I use one of your techniques and I screw up? These steps you describe are a black box to someone who is no git savvy yet. While these definitely help but they propagate the "git is scary, cross your fingers" mentality. What I mean by this is that the reader won't be any wiser after reading
> git reset HEAD~ --hard
What is ~ after HEAD? What is --hard? Is there a --deep option as well?
So I think that you could upgrade this with some annotations over the cryptic parts with a little explanation. What do you think?
- ivanhoe 10y agoOn the other hand all of these options are well documented in the git book and manual, so it's quite easy to check the details you're not sure about (and learn something new in the process).
- Erwin 10y agoAfter all this time the HEAD~ syntax has suddenly started making sense to me -- this is the syntax for backup files in vim, so HEAD~ is the "backup" i.e. previous version of HEAD.