Enabled distributed version control

[GoogleCodeExporter]

Hosting this project on a git-enabled (or otherwise distributed version
control system) site would make it much easier to contribute, since each
developer would have his or her own branch to commit changes to, instead of
just one master and numerous patches being applied to it almost randomly.

Contributing is so much easier when the version control is distributed. I
prefer git, but as far as I know, it should be possible to enable
distributed version control (through Mercurial) on Google Code as well.

Original issue reported on code.google.com by asbjornu on 4 Jan 2010 at 8:23

[GoogleCodeExporter]

this is the model, for now. There's nothing stopping people from contributing 
through
patches.

Original comment by wump...@gmail.com on 4 Jan 2010 at 11:59

• Changed state: Invalid

[GoogleCodeExporter]

Patches is a great deal more messy than each developer having their own branch, 
but 
okay. :)

Original comment by asbjornu on 5 Jan 2010 at 7:29

[GoogleCodeExporter]

Just now I'm having major problems with the fact that the version control isn't
distributed. I've done some changes that I've uploaded a patch for (see Issue 
#19)
and incrementally built on that with other changes I'd now like to "commit" via 
a
patch. Had I been able to actually commit my former patched changes, I'd have a
revision to make a patch from.

Since all of my local changes are uncommited, I don't think it's possible to 
create a
patch of the changes made since my previous patch. So, until my last patch is
accepted, commited and locally updated, I can't really provide any new patches. 
Or is
there a way to create a "patch minus another patch" somehow?

Original comment by asbjornu on 5 Jan 2010 at 3:20

[GoogleCodeExporter]

not sure. try again.

Original comment by wump...@gmail.com on 6 Jan 2010 at 11:48