J�rg Bullmann wrote:
With this I imported two test modules using MacCVSClient, zlib data stream compression level 3. I use a MacCVSClient beta because the current 1.9 cannot cope with truncated paths in server responses.
I didn't put any checks in the server for whether clients could handle the truncated paths because it was already in the client/server protocol spec, but I could have. I think MacCVSClient isn't the only client that had problems with it, though.
Is it going to cause any trouble for you if I go back in add a NULL client response to the protocol that tells the server that a client can handle the truncated specs?
Derek
_______________________________________________ Bug-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-cvs
