Gillis Paul wrote:
> Given that subversion commits are supposed to be atomic, all or
> nothing... can I assume that a commit done with TortoiseSVN has
> completed successfully if I see the new revision in my repository using
> the repo browser even though my TortoiseSVN commit window is still open
> with the OK button greyed out and it hasn't updated itself in the last
> hour or so?
Yes.
> I can see TSVNCache and TortoiseProc processes still running in Windows
> task manager throttling away, but they are only taking up 7-15% of CPU
> and 5-15Mb or memory. I am committing to a repository on a network
> share using the file:/// protocol, but the repository looks updated.
> What the heck is TortoiseSVN doing?!?! My network utilization is almost
> 0.
After the commit, the administrative area is changed to reflect the
fact that changes were committed (pristine copies etc.), so there is
some work to do after commit. If you interrupt the dialog, a cleanup
and an update should do the job. The worst case scenario would be a
corrupted working copy, but since a commit leaves your working files
untouched, even in this case you can copy uncommitted changes to a
freshly checked out WC.
I have no idea why the dialog hangs - I've never seen something
similar before. Solar eruptions?
Kind regards
Sven
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed May 10 22:27:21 2006