On Wed, 9 Feb 2005 10:01:29 +0100, Lübbe Onken <l.onken@rac.de> wrote:
> I think this has (partly) been reported before, but TortoiseSVN (Build 2642,
> latest nightly) doesn't update its file and folder status after a revert.
The cache should work correctly now when files get reverted.
> I have a directory containing some modified files. The modified icons were
> propagated up to the WC root. I selected revert on the WC root and let TSVN
> revert all files, which the progess dialog happily tells me it did. Alas all
> the file / folder status remain modified as before. F5 doesn't change
> anything and if I select revert on the WC root again, all the files are
> offered again. At this point I assume that revert worked and that just the
> cache status is wrong.
>
> Hm, switching to the dos shell:
> 'svn st' shows me that the files are modified even after running tsvn
> revert. What can I believe now? This sounds like revert on the WC root
You should always believe the CL client. ;)
If you're in doubt, use "check for modifications".
> didn't revert files in a subdirectory even if they are shown in the revert
> and progress dialog. Reverting a single file in tsvn yields the same result,
> so it's a general revert / status problem.
> Svn diff and tsvn diff both show that the files are really different, so
> tsvn revert failed in both cases.
- do you have a 'nested layour' in your working copy?
- modified files across svn:externals?
- selecting one file in explorer and calling "revert" doesn't revert
that file either?
> Trying to revert with the cl client now:
> 'svn revert *.h' does revert, because a 'svn st' doesn't list the .h files
> anymore. So that seems to work. Tortoisesvn doesn't catch that status update
> forced by the cl client, because the .h files are still shown as modified.
> Tsvn diff and and svn diff don't show any differences in the files, so the
> revert has worked
Strange. But if I do a revert here on my machine, it works. ???
> Now it's getting worse. I select 'tsvn revert' on my wc root again and the
> files are shown again. Wh...
>
> <sidenote>
> Minutes later, while I am writing this, the cache crawler seems to have
> reached my reverted files, because now the status switched to 'normal' up to
> the WC root. Another reason for priority scheduling.
> </sidenote>
>
> ...en I now 'tsvn revert' the files, they are back in the *modified* state.
> Yes, no typo, *modified*. This sounds like tsvn revert is doing the opposite
> of what it is supposed to do.
> 'Svn st', svn diff and tsvn diff confirm that the files are back to the
> modified state.
I have no idea how TSVN could modify a reverted file again?
What I noticed when doing a 'revert' on the TSVN wc root was that it
took a whole minute(!) for the revert dialog to populate all the
modified files! And then the revert took as long.
Seems to me that the cache while crawling the tree somehow blocks
other Subversion commands (tree is locked?).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Feb 9 11:10:30 2005