Hi Ben, As an experiment, try these things: > > 1. Commit from a different network, but same computer (assuming > computer is portable) > > 2. Commit from a different computer, but same network. > > 3. Commit from same computer and network, but to a totally different > svn service. >
Thanks for all these suggestions. I was going to start doing some of these once I had tested out connection here, etc. :-) However, it turned out that switching from SVNKit v1.2.0.4710 to JavaHL v1.5.2 (r32768) did the trick. Very weird. A couple of possibilities I suppose is that maybe SVNKit being pure Java was taking longer to process information and some time-out was triggered perhaps or maybe time-out settings are just different between the two. Any ideas?? I know I should switch back to SVNKit and see if the problem re-occurs. I'll do this if you want to pursue this further but, for now, I'm just happy that I can get on with committing again. :-) :Darren. -- ---------------------------------------------------------------------- :Darren :Pearce ---------------------------------------------------------------------- *** Shop & Donate: http://buy.at/campuskids *** ---------------------------------------------------------------------- [email protected] Postdoctoral Researcher London Knowledge Lab, University of London ---------------------------------------------------------------------- [email protected] Visiting Research Fellow Informatics, University of Sussex http://www.informatics.sussex.ac.uk/users/darrenp/ ---------------------------------------------------------------------- [email protected] http://www.linkedin.com/in/darrenpearce ------------------------------------------------------------------------
You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
