Comments on: Dabbling in distributed version control

By: Darcy Casselman

Darcy Casselman — Wed, 21 Jan 2009 11:46:44 +0000

I gotcha. I’m talking about people who get stuck in one version control paradigm having weird expectations when they move to another. As far as I can tell, the answer to being put off by long, sha1 hash strings for version numbers is you probably never actually need to refer to version numbers. Particularly in a distributed system.

By: ikegami

ikegami — Wed, 21 Jan 2009 01:18:23 +0000

I’m not talking about tags. I’m talking about the actual version numbers. Here’s an example:

http://perl5.git.perl.org/perl.git/commit/e0d6880329cb1f7117561b49a7703b366f265dc3

By: Darcy

Darcy — Tue, 20 Jan 2009 04:51:47 +0000

Congrats on finding a job! :D

I wouldn't have thought you'd have to deal with the SHA1 hashes very much. Unless you're trying to do something in git that you used to do with Perforce... We ran into people like that at my old job, who came from CVS and thought you had to obsessively tag everything all the time...

Git's quite a bit better on Windows now, but the unsupportedness of git-svn and the general hackishness of the whole thing was kind of a turnoff. I took a look into the APIs a bit and left with a bit of a bad taste.

Bzr is nice. I think I'll stick with that.

By: ikegami

ikegami — Mon, 19 Jan 2009 23:04:10 +0000

I just had a crash course in Subversion today. (First day on the job!)

Perl5 has just moved from Perforce to Git. The long version numbers (sha hashes) are causing some (mostly visual) issues. Turns out you can truncate the number in most places.

By: matt

matt — Mon, 19 Jan 2009 22:58:03 +0000

I vote Bazaar, but then again, I don't need Visual Studio integration...

Also, my needs aren't that strenuous... so it fits pretty well.

Tried Mercurial for a bit, but didn't like it.

Need Windows support, so Git never really entered into the picture... (It's probably come quite a way, but it seemed REALLY rooted in Linux the last time I looked...)

Best of luck!