I'm the maintainer of Unison at https://github.com/bcpierce00/unison. There, we only support the latest formal release and master. We're currently heading for another point release.
I'd like to have it be clearly understandable how this relates to up-to-date unison. if it's still relevant, which I think it is, then I'd like to be able to put in a link from https://github.com/bcpierce00/unison/wiki/Software-for-use-with-Unison that has a one-line description of what and when it is intended to be used.
There's also the question of whether this should be upstream; I don't have any agenda there, but I don't want to cause the upstream build to have any new dependencies. So I am guessing this remaining separate is the right path, but we're open to discussion on unison-hackers.
Formally, this is a bug report that reading the README I can't tell 100% what's going on, as it talks about 2.48, and 2.48 is formally not relevant upstream. I suspect it's easy to address, by someone who does understand.
I'm the maintainer of Unison at https://github.com/bcpierce00/unison. There, we only support the latest formal release and master. We're currently heading for another point release.
I'd like to have it be clearly understandable how this relates to up-to-date unison. if it's still relevant, which I think it is, then I'd like to be able to put in a link from https://github.com/bcpierce00/unison/wiki/Software-for-use-with-Unison that has a one-line description of what and when it is intended to be used.
There's also the question of whether this should be upstream; I don't have any agenda there, but I don't want to cause the upstream build to have any new dependencies. So I am guessing this remaining separate is the right path, but we're open to discussion on unison-hackers.
Formally, this is a bug report that reading the README I can't tell 100% what's going on, as it talks about 2.48, and 2.48 is formally not relevant upstream. I suspect it's easy to address, by someone who does understand.
-- gdt (Greg)