Git

hidas on 2012/05/10 01:58 of Blob Entertainment System

This is the second time I've used Git on a project, and I am liking it more and more.
I haven't had the good fortune to have to use the reset command yet, but I think that as I grow more and more used to the "git workflow", I'll be able to use my time more efficiently.
The ability to have an up-to-date copy of my work on any computer is really useful; and to be able to update the "main" repository from any computer, (in my case any operating system).

(log in to comment)

Comments

davec on 2012/05/10 05:40:

It's great, isn't it? I've been using it for the first time this PyWeek after using Subversion for what seems like forever. I'm a convert too!

mauve on 2012/05/10 06:33:

Mercurial all the way for me :)

richard on 2012/05/10 09:36:

mauve speaks truth. I'm using git this comp because my team-mate only knows it and I'm already sick and tired of the obscure error messages and strange command names :-)

superjoe on 2012/05/10 16:06:

I think I agree with the mercurial users. The popularity of git is hard to ignore though.

davec on 2012/05/10 18:16:

In the interest of fairness I will use mercurial for my September PyWeek entry and see how it compares!

Cosmologicon on 2012/05/10 20:25:

I've been using version control on all my solo PyWeek and Ludum Dare games for years now, and you know what? It's never paid off. I've never once reverted anything or compared revisions or anything useful like that. The only thing I get out of it is an easy way to back it up to an online repository, and this could be done better with an online backup service that auto-updates.

I pretty much only use it because everyone swears up and down that it's worth it, and I don't want it to look like my dissenting opinion is out of ignorance or inexperience.

But that's just for solo projects, of course. For team projects, version control is obviously the only way to go.

superjoe on 2012/05/10 21:16:

"I don't want it to look like my dissenting opinion is out of ignorance or inexperience."

I wouldn't judge you for this. I strongly believe that it is worth it for me, but I don't find it hard to believe that your development methodology is different from mine such that it is not worth it for you.

The two features I use that make it totally worth it for me:

  • "okay, I'm back... now where was I?" (git diff)
  • "well. that stuff I just spent 12 minutes coding broke everything, and I don't remember what all I did." (git checkout .)