> 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?
You say that it got 'almost' done. At what stage was the commit when it
died? If it was at the very last step, then the commit could have been
successful but only the post-commit hook script did not finish. In that
case, your working copy would still think the commit failed, but the
repository already had a successful commit.
Just update your working copy.
And maybe you should consider setting up an svn server instead of using
a flaky VPN connection.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-05-31 08:26:01 CEST