Grokking Git ** UPDATED ** 03/30/2009

** Updated X 2 ** 03/30/2009: James Bennett just posted slides from his talk about DVCS. Seems like he comes to some of the same conclusions as me. Blog post here.

** Updated ** 10/08/2008: L O L

So I get why git is a great tool for OSS development. The ability to easily fork, change, merge, sync and re-branch a seemingly infinite amount of times is valuable when you probably won’t know all of the collaborators / developers.

But what part of Git is useful / different from SVN if you know everyone involved? Or, more simply, why should I use git for my internal source control system?


Comment on the post “Lots of Yammering. Will businesses buy it?“:

“I think someone should come out with a completely new enterprise communication system. Take Twitter, Facebook, Wikipedia, etc and build them into one platform that’s integrated with LDAP and can be integrated into legacy systems. Not sure why this isn’t being done yet.”

Not sure what the funniest part of that quote is: the “etc”, the “not sure why..” part or the thought that the same customers that block IM internally would jump at a twitter / fb like platform.

Timely Quote

“It is the soldier, not the reporter, who has given us freedom of the press. It is the soldier, not the poet, who has given us freedom of speech. It is the soldier, not the campus organizer, who has given us the freedom to demonstrate. It is the soldier, not the lawyer, who has given us the right to a fair trial. It is the soldier, who salutes the flag, who serves under the flag, and whose coffin is draped by the flag, who allows the protester to burn the flag.”

— Father Dennis Edward O’Brien, USMC