<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Yes, moving to Github might be a reasonable step at this point — it would certainly simplify issue tracking, among other things. <div><br></div><div>One specific technical issue needs to be sorted out to make this happen: The way that Unison’s version number is embedded in the code (so that the binary knows which version of the source it was built from) is quite SVN-specific. If people feel motivated to help with a move to github, taking a look at how this might best be done in the Git context (manually? by somehow approximating what SVN does? by some different automatic mechanism?) would be a big step in the right direction.</div><div><br></div><div>The file mkProjectInfo.ml is the place to look. Should be self-explanatory.</div><div><br></div><div> - Benjamin</div><div><br><div><br><div><div>On Oct 27, 2014, at 5:35 PM, E. Timothy Uy <<a href="mailto:tim@loqu8.com">tim@loqu8.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">I would propose something standard like GitHub to host everything and track bugs.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 27, 2014 at 2:25 PM, Benjamin C. Pierce <span dir="ltr"><<a href="mailto:bcpierce@cis.upenn.edu" target="_blank">bcpierce@cis.upenn.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There are certainly other bugs and missing features (check the archives of the mailing lists for suggestions — there’s also a TODO file, but it’s pretty old), but this is the only correctness-critical one that I’m aware of at the moment.<br>
<br>
For a good overview of how Unison works internally, see the tech report “What’s in Unison” by me and Jerome.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Benjamin<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On Oct 27, 2014, at 4:48 PM, <<a href="mailto:moonkid@posteo.org">moonkid@posteo.org</a>> <<a href="mailto:moonkid@posteo.org">moonkid@posteo.org</a>> wrote:<br>
<br>
> Dear Benjamin,<br>
><br>
> if this is really the "easiest bug" you currently have - Unison is<br>
> nearly perfect. :D<br>
><br>
> The problem you described is kind of to hot for me. I wrote some<br>
> sync-stuff for myself, too and know how disastrous small modifications<br>
> could be (losing TBs of data!).<br>
><br>
> I am not sure but maybe it is a little bit to much for me to start.<br>
><br>
> But...<br>
> Is there a detailed documentation about the sync-process, the checkings<br>
> and decisions of the algorithm? Is there a human readble text (not the<br>
> code) to understand how the algorithm work?<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>
<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>
</div></div></blockquote></div><br></div>
_______________________________________________<br>Unison-hackers mailing list<br><a href="mailto:Unison-hackers@lists.seas.upenn.edu">Unison-hackers@lists.seas.upenn.edu</a><br>http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers<br></blockquote></div><br></div></div></body></html>