[Unison-hackers] Move Unison to Git

[Benjamin C. Pierce]

I must admit I'm not too excited about moving Unison to a different version control system.  We've done it twice before, and each time it took two or three full days of fiddling before everything was completely working again.  (It's not just a matter of moving the sources: the VCS is also involved in the version numbering mechanism, the procedure for remembering what's changed for inclusion in release messages, the mechanism for building and exporting new releases, ...)  

If there are active maintainers / compilers of Unison distributions who feel that they could do their jobs more effectively with commit rights to the main SVN repository, just let me know and we can make that happen.  

Best,

    - Benjamin


On Feb 9, 2011, at 9:28 AM, Pascal Bach wrote:

> Hello
> 
> I noticed that there are a lot of patches floating around in the
> unison-users mailing list especially for build purpose. And what I
> know from the (Non-)development status page unison isn't actively
> developed anymore but patches are still welcome.
> 
> I think in the current situation a distributed version control system
> would be more useful as it would facilitate the inclusion of patch for
> other people than the maintainers.
> I thus propose that the main repository should switch to Git
> (Github.com or Gitorious.org for example).
> 
> I already setup a mirror of the SVN repository on github were I keep a
> branch with some build patches. https://github.com/pascal-bach/Unison
> 
> Please let me know what you think about my proposal.
> 
> Best regards
> Pascal
> _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers