On Oct 29, 2010, at 19:00, Daniel Shahaf wrote:
>> I suppose we should report the problem to Google Code and hope they
>> can uncorrupt the repository somehow?
>
> Yes. SVN_ERR_FS_CORRUPT justifies reporting this to the Google admins.
To provide some closure, Google did not respond to the supp
Ryan Schmidt wrote on Fri, Oct 29, 2010 at 18:26:25 -0500:
> On Oct 29, 2010, at 17:11, Daniel Shahaf wrote:
>
> > Short version: it's a bug in Google's backend, and I can reproduce it
> > with neon but not with serf.
>
> > % $svn log -v -r2967 http://pure-lang.googlecode.com/svn/trunk
> > --con
On Oct 29, 2010, at 17:11, Daniel Shahaf wrote:
> Short version: it's a bug in Google's backend, and I can reproduce it
> with neon but not with serf.
> % $svn log -v -r2967 http://pure-lang.googlecode.com/svn/trunk
> --config-option servers:global:http-library=serf
> ---
Short version: it's a bug in Google's backend, and I can reproduce it
with neon but not with serf.
(more below)
Ryan Schmidt wrote on Fri, Oct 29, 2010 at 16:24:20 -0500:
> The Pure project is trying to switch from Subversion to Mercurial, and are
> having trouble with svnsync.
>
> http://grou
