Ayende @ Rahien

Unnatural acts on source code

Git for OSS projects

If I needed more reasons to move to Git, this would be it:

image

Just to make things more interesting, a couple of those are pull requests, but the middle is just a patch that I got sent. That patch also include a binary file.

Automatically tracking who did what and where, even for people who aren’t members of the project? Not having to handle binary files in patches in a special way?

That is just makes things so much simpler…

Comments

Frank Quednau
09/14/2009 07:56 AM by
Frank Quednau

following your efforts with Divan-DB I got myself a github account. I can't say I grok all the new possibilities with git yet but am hoping for aha-moments that will inevitably come.

Andrey Shchekin
09/14/2009 03:30 PM by
Andrey Shchekin

One thing that would solve a lot of problems Subversion has with OSS projects would be to have check-in moderation queue built-in in SVN server.

So instead of sending a patch, you could just commit (choosing a name). And if the check-in is approved, it would be included with your name and you will be visible as committer. This would not allow for full GIT flexibility, but would fix most problems while preserving centralized Subversion model.

Tim Barcz
09/14/2009 06:28 PM by
Tim Barcz

Nice...I like how you choose my "n00b" comment as the one to display...

Many thanks...haha

Jafin
09/16/2009 09:48 PM by
Jafin

Also consider Mercurial, GoogleCode apparently has support for it now ( googlecode.blogspot.com/.../...le-to-all-open.html)

One reason why is Mercurial apparently has a better Windows story at the moment than Git. Pretty much everything else is on par.

Comments have been closed on this topic.