I've got the SVN running on a server on a private network. I committed
(with TSVN) from my computer not on that private network, but
connected through VPN. Hence the problem that when my VPN dies, my
commit is interrupted. Now for whatever reason (I'm guessing since the
records were added even though the content wasn't finished) my local
copy says it's up to date, and when I try to commit it says there's
nothing to send. If I try to update it says there's nothing to
update...
How can I fix this?
On May 31, 10:21 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
> Jeff wrote:
> > It was in the middle of sending content. So it had already finished
> > "adding" the files to the svn, but it hadn't finished sending them.
> > The svn server is on a private network...that's why i need the vpn to
> > get in. Surely tortoisesvn is smart enough to recover from a network
> > interruption?
>
> Yes, it will handle such situations just fine. But of course only if
> everything is set up correctly.
> I'm wondering, are you connecting to your private network and executing
> TSVN there? If then the network connection dies, isn't TSVN still
> running on your PC in your private network?
> If you run TSVN locally and connect to a remote server, then your local
> working copy should know that the repository does not have the full
> commit (and the repository will definitely know).
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
>
> signature.asc
> 1KDownload
---------------------------------------------------------------------
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 17:47:42 CEST