UWN

Great, I'm still in Paris back from a nice day and a nice evening! And it's all fixed!

> I will restore the old repo though in a while, for reference purposes. This will not restore the cross-links with other projects AFAIK. They are just lost. So for...

In any case, all the issues are lost.

It [seems](https://stackoverflow.com/questions/9247961/recover-a-deleted-repository-github-issues) there are ways to recover issues.

@infragdig: According to a response from github, only the owner can restore a repository including their issues. And that within 90 days. So you would need to restore it somehow.

Since you have not recreated the old issues, I will from now on report issues as Items on my site. This, to start with, is Item#1

According to the github support team you can restore within 90 days. So please do this.

Does it really make sense to copy the improvements that happened for Scryer's clpz piece-by-piece? Wouldn't it be better to take all of them in one fell swoop?

``` ?- X #= sign(X). clpz:(X#=sign(X)), clpz:(X in-1..1). % clpz:(X#=sign(X)) not needed ``` Whenever X is -1..1 or less, replace sign(X) by X.

@triska: Is this too difficult to integrate? ``` ?- X #= sign(X). clpz:(X#=sign(X)), clpz:(X in-1..1), unexpected. clpz:(X in-1..1). % expected X in-1..1. % alternate formulation