[Unison-hackers] BugTracker?

[E. Timothy Uy]

I would propose something standard like GitHub to host everything and track
bugs.

On Mon, Oct 27, 2014 at 2:25 PM, Benjamin C. Pierce <bcpierce at cis.upenn.edu>
wrote:

> 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.
>
> For a good overview of how Unison works internally, see the tech report
> “What’s in Unison” by me and Jerome.
>
>     - Benjamin
>
>
>
> On Oct 27, 2014, at 4:48 PM, <moonkid at posteo.org> <moonkid at posteo.org>
> wrote:
>
> > Dear Benjamin,
> >
> > if this is really the "easiest bug" you currently have - Unison is
> > nearly perfect. :D
> >
> > The problem you described is kind of to hot for me. I wrote some
> > sync-stuff for myself, too and know how disastrous small modifications
> > could be (losing TBs of data!).
> >
> > I am not sure but maybe it is a little bit to much for me to start.
> >
> > But...
> > Is there a detailed documentation about the sync-process, the checkings
> > and decisions of the algorithm? Is there a human readble text (not the
> > code) to understand how the algorithm work?
> > _______________________________________________
> > Unison-hackers mailing list
> > Unison-hackers at lists.seas.upenn.edu
> > http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers
>
> _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.seas.upenn.edu/pipermail/unison-hackers/attachments/20141027/bb306ab2/attachment-0001.html>