Category Archives: git

The results from last week’s poll are in! And they couldn’t be more (less) clear: A highly unscientific poll shows an even split between true and false, with a minority choosing the other two options. So that settles it! What’s … Continue reading →

I’m curious to see what folks set as their default core.autocrlf settings in git (for those of us who use msysgit on Windows): http://twtpoll.com/tts3oj I have a feeling that we need a sensible default, but have seen lots of opinions … Continue reading →

I love Git. It’s very powerful tool that lets me bend my repository to my will, with commands and features that blow the other source control providers I’ve used out of the water. However, the tooling just doesn’t do it … Continue reading →

I had a rather large number of remote repositories set up in my Backbone.ModelBinding repository on my box, due to the wonderful community of contributors. But it was time for me to clean out the remotes as I no longer … Continue reading →

Earlier this month I had the opportunity to record an episode of Herding Code with GitHubbers Paul Betts and Phil Haack on the state of Git for Windows: Herding Code 132. Topics included discussions on why Git hates developers and … Continue reading →

I got tired of manually typing “git push origin master” and “git push heroku master” to push changes in my BBCloneMail app up to Github and then deploy to Heroku. So I automated that with a rake task. Then I … Continue reading →

Jimmy’s post is a nice reminder of the advantages of a distributed version control system. But having ramped up on Git primarily through git-svn, I thought it would be worth enumerating some of the advantages I’ve found just in my … Continue reading →

Just a reminder that the D in DVCS stands for “Distributed”, not “Disconnected” or “Decentralized”. This is a centralized model (from http://progit.org/book): And this is Distributed: Note that in the first picture, you’re reliant and dependent on the server for … Continue reading →

I’ve been working with git-tfs on a project for about a couple of months. Git-tfs is a source control bridge that allows you to work with Git locally, reducing the number of operations to communicate with the TFS source control … Continue reading →

Having done quite a bit of branching in centralized and distributed source control systems, I’m intimately aware of the additional (and I would say, unnecessary) pain centralized source control systems like Subversion and TFS bring to more powerful branching strategies … Continue reading →