[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Interrupted Commit issues

From: Alf Christophersen <alf.christophersen_at_medisin.uio.no>
Date: Sat, 31 May 2008 07:37:59 +0200

Jeff wrote:
> Ok folks...im about to lose my mind.
> A while back our old svn db got horribly corrupted. After spending
> days trying to recover it, I decided to give up and start from
> scratch. In doing so, I have roughly 30000 files in 800MB to recommit
> into the new repo. Unfortunately, I can only connect to send these
> files through a horribly iffy VPN connection. The VPN typically
> disconnects me after about an hour.
> So I went through the procedure and started the commit...it got ALMOST
> done...and my VPN connection died. So obviously the commit timed out.
> Now the problem is, when I go to commit a second time, it says that
> everything is already there and up to date...but I KNOW that all the
> content isn't there.
> How can I finish the commit?
Sounds like you use file: protocol?? In case, set up a svn-server and
use svn-protocol.

In one of my projects at work I used file protocol and it was soooooo
slooooooow, compared to my spare time project in cooperation with some
other spare time programmers working with php-based web scripts where
commiting was just a second or two.
Then I changed to svn-protocol since svn was installed at the server,
and suddenly, uploading just take a few seconds.


To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-31 07:38:12 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.