Simon Large wrote:
> Whilst checking out how nested WCs work I discovered a feature, using
> build 3402.
>
> Create a new folder inside an unmodified WC.
> Checkout a small project into this new folder.
> Modify a file in the new folder.
>
> Now the new folder behaves as a normal WC, and shows a modified icon.
> The new folder is not a child of the containing WC, so if you try to
> commit the parent folder TSVN shows you a message that there is nothing
> to commit. Check for modifications confirms this. So far, correct.
>
> The containing WC shows a modified icon, even though check for
> modifications shows there are no mods. Is this what we expect to happen?
>
> In one way it is good because it alerts you to the fact that there are
> uncommitted changes in the nested WC.
>
> In another way it is bad because the behaviour is inconsistent.
I know this is inconsistent. But in the first versions of the cache, it
was even worse: *all* parent folders got the overlay, even unversioned
folders and the drive icon ;)
Now we at least check first if the parent is versioned before we
propagate the child status upwards. But that's all we do. And I think
that's all we *can* do without adding a huge check/validation routine to
the cache, which of course will slow it down remarkably.
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 Sat May 21 16:58:15 2005