> This particular error message has been discussed many many times. > It's going away, so lets not get into it in great detail. The problem > is that the code must be cross-protocol and there is not alway a > useful error message to report. That particular check covers MANY > problems and it is not always possible to know precisely which of them > is happening. You know - it might be useful to say something just a bit more specific. Like: something is wrong with: your connection the server your worldview your politics etc. ok so just the first two, really. but something to relate that the problem is at the repo or in your connection to the repo and not just a problem with the world. what do you think? -sv
