Derek Price writes:
Since we're not actively testing new clients against old servers, I
would hazard that no matter how hard we've been trying to maintain
legacy support that far back, much of it is going to turn out to be
broken anyhow.
On the contrary, I suspect it mostly works fine. When dealing with public
repositories, there's no telling how ancient a client might try to
connect to a new server or how ancient a server you might want to access
with a new client. Unless there's some *major* benefit to removing the
backwards compatibility code, I say we leave it alone.