Russell Hind wrote:
>
> If I then browse in to External 3, the file then changes to modified,
> and then if I back out, External 3, Common and Project all have a
> modified flag, but it was only triggered by me entering the modified
> external directory, not be the cache crawling as expected.
>
I forgot to add, if I leave an explorer window viewing the contents of
Common, and wait for over 10 minutes (the timeout) then back up to
Project, Common changes from modified to unmodified (cache timeout) but
never changes back again, I guess because the cache doesn't crawl the
external. The only way to get a modified back on 'Common' is to browse
in to the external directory with a modified file again and then back out.
We could take the approach here that 'Common' should never be marked as
modified when only an external is modified, so in that case the code
that propogates 'modified' status back up the tree needs to spot externals.
But I'd rather Common did show the state of the externals. I realise I
can't commit from common, I have to go in to it and commit each external
individually, but it is extremely helpful to have that indicator on
Common that one of the externals has changed, so I'd rather see the
cache modified to reflect the state of all sub-working copies, even if
they aren't direct children of the folder as in this case.
Cheers
Russell
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed May 4 14:17:10 2005