git commit –amend: Have Your Cake and Eat it Too

For a lot of us, version control does two things which are contradictory: it keeps checkpoints as we work so we can easily roll back, and wraps up our work into a tidy package for others to use. git commit --amend is one tool that solves this. It will "open up" the previous commit, adding staged … Continue reading git commit –amend: Have Your Cake and Eat it Too →

My Problem with Git: No Abstraction

Git is powerful, and Github is its killer app. I use them for all my projects. That being said, Git is more difficult than it ought to be, but until now I couldn't put my finger on why I was doing some mundane Linux command line work when I had my flash of insight. I've … Continue reading My Problem with Git: No Abstraction →

That one little confusing thing about the Git version control system

Git and github are awesome pieces of software. Last year, I happily switched from subversion to git just like, years ago, I switched from CVS to Subversion. Another evolutionary step. I use GitHub for lots of reasons. The biggest is that it's the best front-end to git that I've found. And so now I use … Continue reading That one little confusing thing about the Git version control system →

Why "git" instead of "svn"?

As I learn git, I'm experiencing advantages that I haven't seen described together. Also, I haven't seen a description from the perspective of the real-world differences in your files, so here goes: Background context Subversion uses a single, central repository which is in a remote place. And in your project, it maintains .svn/ directories in every … Continue reading Why "git" instead of "svn"? →