[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: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sat, 31 May 2008 18:21:28 +0200

Jeff wrote:
> 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?

I have a hard time believing that this is all you did. Subversion was
*designed* to handle network interruptions (because that's one of the
things that were very bad in CVS). There must be something else you did.
Subversion would never mark working copy modifications committed if the
client does not receive the final ok from the repository. The same for
the repository: it won't include/add/do-whatever-you-ask if it does not
get the last 'now-i'm-finished' from the client.

Maybe you should ask on the Subversion mailing list for help.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

Received on 2008-05-31 18:21:47 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.