Mercurial

[GoogleCodeExporter]

Any interest in switching source control to Hg? Would make things easier to 
work on branches for contributions / patches etc.

Original issue reported on code.google.com by kar...@gmail.com on 4 Apr 2012 at 2:49

[GoogleCodeExporter]

I was actually thinking of git... Not much experience with either though.

Original comment by yuriastrakhan on 4 Apr 2012 at 2:51

[GoogleCodeExporter]

Either is fine - Hg has a bit better windows support, and I quite like kiln for 
hosting my projects.

Working on porting the library to run on mono at the moment... surprised how 
many small nuances there are.

Original comment by kar...@gmail.com on 4 Apr 2012 at 3:34

[GoogleCodeExporter]

Sounds good! At some point it should probably start using built-in memmapped 
file access -- Mono supposedly already supports that API - 
http://www.mono-project.com/Release_Notes_Mono_2.8

As for win support - I might be mistaken, but i thought git had much more 
active .net bindings projects (will have to look it up). But yes, I was 
planning on migrating sometime very soon. Still more inclined towards git, but 
will have to research it some more.

Original comment by yuriastrakhan on 4 Apr 2012 at 3:41

[GoogleCodeExporter]

the native memmapped would help quite a bit... but we're not there yet - 
several mono compiler errors prevent it from building, but easily patched 
around those - now researching why the cecil output leads to segfaults. I am 
trying to develop this at home on a mac, but monodevelop is no visual studio...

Original comment by kar...@gmail.com on 4 Apr 2012 at 4:04

[GoogleCodeExporter]

IL & Expression trees code generation + direct unsafe memory access + 
pinvokes... There is plenty to segfault out there... :)  Let me know.

Original comment by yuriastrakhan on 4 Apr 2012 at 6:00

[GoogleCodeExporter]

Migrated to GIT, will see how well that works

Original comment by yuriastrakhan on 4 Apr 2012 at 2:49

• Changed state: Fixed