Re: GitHub svn bridge corrupting working copies

2017-10-15 Thread Daniel Shahaf
Ryan Schmidt wrote on Sun, Oct 15, 2017 at 14:00:10 -0500: > On Oct 15, 2017, at 13:07, Daniel Shahaf wrote: > > Ryan Schmidt wrote on Sun, 15 Oct 2017 12:49 -0500: > >> And the problem will just occur again sometime later with a different > >> node. The node it complains about is always a directo

Re: GitHub svn bridge corrupting working copies

2017-10-15 Thread Ryan Schmidt
Thanks for your suggestions! On Oct 15, 2017, at 13:07, Daniel Shahaf wrote: > Ryan Schmidt wrote on Sun, 15 Oct 2017 12:49 -0500: >> And the problem will just occur again sometime later with a different node. >> The node it complains about is always a directory that someone else >> committed

Re: GitHub svn bridge corrupting working copies

2017-10-15 Thread Daniel Shahaf
Ryan Schmidt wrote on Sun, 15 Oct 2017 12:49 -0500: > And the problem will just occur again sometime later with a different node. > The node it complains about is always a directory that someone else committed > to recently, [...] Have you looked at these commits? Is there anything unusual in t

GitHub svn bridge corrupting working copies

2017-10-15 Thread Ryan Schmidt
Hi, I'm sure this is GitHub's problem, because it happens only when accessing a git repository through the GitHub Subversion bridge using the Subversion client, but it's been months since I reported the problem to them and they haven't fixed it so I thought I'd ask here if anybody has any idea h