> You cannot update a directory without also updating its children. The
> Subversion working copy format does not support that concept. CVS
> does not version folders so cannot really be used as a comparison. In
> our testing of CVS, it handled files the same way that we do (with the
> exception of the folder problem). But if a file was changed in many
> versions, you do not see the changesets for anything but the latest
> I did not write any of this code, but I seem to recall that the
> Synchronize view itself, does not allow a file to belong to more than
> one changeset. That is why we cannot simply include it in each
> changeset. I could be wrong about that. The Subversion API only
> tells us the latest version of the file in the repository so there
> would be no way to know it belonged to any other revisions anyway, at
> least not without running svn log on every file in the view.
then i guess the big behavior difference in subclipse plugin and cvs plugin
at least how we notice it is because of dirs.
Can we have an option that dirs are never updated with a change set?
But only the files? Because if the dirs are updated then anything that is
can also go with it and that is not what one expect to happen if you just
update these files.
the same for properties of a dir. That is a "file" of the dir right? Is it
to update only that instead of the dir (and all the children) itself?
Then after i updated all the changesets i can do a global update to really
also update all the folders.
Received on 2008-11-11 15:36:27 CET