I've fixed FileHandler/UncompressedFileHandler.cs so the associated unit
Clayon, it looks as if at some point you changed the EOF test to terminate
on a blank line. Was this an accident or was there a good reason for doing
this? I've now changed this test back to the way it was. Hope this
doesn't break something else.
Seeing as we are about to do an official release, I thought I had better
change Requests/ValidResponsesRequest.cs to only report those responses
that we do actually support. This then allowed the Requests test to
succeed. However, real cvs servers then failed to talk to us, so I now
claim we also support 'Merged' and 'Removed' responses even though we
don't. This means the Requests test fails again. If during testing you
get a message of the form "E response '?????' not supported by client" then
this response will also need adding to this request.
Also updated commands/LogCommand.cs. This has support for filesets. As is
the case (I believe) with other commands, it is the callers responsibility
for populating the fileset.
Also updated a few of the tests to fix minor bugs and replace some Assert's
Finally I've been having some unusual problems while using anonymous access
I can't seem to find my very latest updates here (using
CvsChangeLog/SharpCvsLib). Is this a physically separate repository to
what we access when we use :ext: which is only updated periodically?
Also using CvsChangeLog/SharpCvsLib I often get "Unknown server reponse
: ><" when trying to access this repository, when I have no problems
accessing a local :pserver:. This seems to happen at random (about 75% of
the time) and may be timing related or could be to do with one of my firewalls.
Any ideas/suggestions gratefully received, as it is begining to get annoying.