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

RE: Re: Interrupted Commit issues

From: Thompson, Graeme (GE Infra, Aviation) <Graeme.Thompson_at_ge.com>
Date: Wed, 4 Jun 2008 03:11:13 -0400

> -----Original Message-----
> From: Alf Christophersen [mailto:alf.christophersen_at_medisin.uio.no]
> Sent: 31 May 2008 06:38
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Interrupted Commit issues
>
> 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.
>

Which protocol you are using to access the repository?

Graeme

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-06-04 09:12:29 CEST

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