Sounds great! I've been VERY happy with github.<br><br><div><br><div class="gmail_quote">On Wed, Feb 9, 2011 at 9:28 AM, Pascal Bach <span dir="ltr"><<a href="mailto:pasci.bach@gmail.com">pasci.bach@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello<br>
<br>
I noticed that there are a lot of patches floating around in the<br>
unison-users mailing list especially for build purpose. And what I<br>
know from the (Non-)development status page unison isn't actively<br>
developed anymore but patches are still welcome.<br>
<br>
I think in the current situation a distributed version control system<br>
would be more useful as it would facilitate the inclusion of patch for<br>
other people than the maintainers.<br>
I thus propose that the main repository should switch to Git<br>
(Github.com or Gitorious.org for example).<br>
<br>
I already setup a mirror of the SVN repository on github were I keep a<br>
branch with some build patches. <a href="https://github.com/pascal-bach/Unison" target="_blank">https://github.com/pascal-bach/Unison</a><br>
<br>
Please let me know what you think about my proposal.<br>
<br>
Best regards<br>
Pascal<br>
_______________________________________________<br>
Unison-hackers mailing list<br>
<a href="mailto:Unison-hackers@lists.seas.upenn.edu">Unison-hackers@lists.seas.upenn.edu</a><br>
<a href="http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers" target="_blank">http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers</a><br>
</blockquote></div><br></div>