Ian Zimmerman wrote:
> It also looks similar to #512710, but since this repository can be
> successfully cloned with svn clone, it is hard to call it "corrupted".
I have never heard of the "svn clone" command. "svn checkout" reads
the latest revision and does not look at earlier history. I tried
using the subversion equivalent to git svn clone, which is "svnrdump
dump" from Subversion 1.7:
$ svnrdump dump \
http://mlton.svn.sourceforge.net/svnroot/mlton >/tmp/mlton.dump
* Dumped revision 0.
* Dumped revision 1.
* Dumped revision 2.
[...]
* Dumped revision 538.
svnrdump: E175002: REPORT of
'http://mlton.svn.sourceforge.net/svnroot/mlton': Could not read response body:
Connection reset by peer (http://mlton.svn.sourceforge.net)
The revision where it stops varies from one run to another.
The above suggests a flakey Subversion server.
I'd recommend finishing the import using "git svn fetch".
Hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
