Re: BugTracker?
"Benjamin C. Pierce" <[email protected]>
| Newsgroups | gmane.network.unison.devel |
|---|---|
| Message-ID | <[email protected]> |
Yes, moving to Github might be a reasonable step at this point — it would certainly simplify issue tracking, among other things.
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.
The file mkProjectInfo.ml is the place to look. Should be self-explanatory.
- Benjamin
On Oct 27, 2014, at 5:35 PM, E. Timothy Uy <[email protected]> wrote:
> 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 <[email protected]> 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, <[email protected]> <[email protected]> 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
> > [email protected]
> > http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers
>
> _______________________________________________
> Unison-hackers mailing list
> [email protected]
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers
>
> _______________________________________________
> Unison-hackers mailing list
> [email protected]
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers
_______________________________________________
Unison-hackers mailing list
[email protected]
http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers