Simon Large wrote:
> Whilst checking out how nested WCs work I discovered a feature, using
> build 3402.
> 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.
>
> What do you think?
I think the actual inconsistency is in the fact that you can move
working copy folders around, but that they wont commit/update in a
nested fashion when placed within each other.
I know that there have been a few people on this list that've said
they were happy with this feature, but they've all been sort of
misguided about the way that they use their working copy.
I can't see any real use cases for placing WC folders inside other WC
folders and then have them *not* be touched when doing operations on
the parent folder.
I consider this a flaw in Subversion, and I don't think anything
should be done to make the cache mimic that flaw.
All in all, it's a good thing that the cache alerts the user that
there are nested items that has modifications, and the fact that
Subversion doesn't update/commit them is just something we'll have to
live with.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat May 21 17:31:56 2005