> 3. (optional) Support efficient use of working-copy-side data when
> update receives a rename. This is merely a matter of
> performance, not correctness. The idea is that if the RA layer
> transmits a rename from server to client, and the client already
> has the source, then the server can just tell the client to mv
> the source to the dest, and maybe apply a diff if there are
> modifications too.
One of the reasons I want true rename support is because
I (in my ignorance, perhaps), think it could solve one
of the major pains of mixed mode unix / windows use
of subversion: the very specific case of someone renaming
a file and changing only the case.
If such an operation in the repository was reflected to
the working copy as a rename during update and revert
(and hence to the OS as a MoveFile operation) this
would work under windows.
And since our commit hook prevents people from committing
multiple files with names differing only in case, but can't
possible prevent people (especially windows users) from
committing files with the wrong case, this is a real
problem.
So step 3 is important to my non-voting, non-counting,
insignificant self-- and I would claim it is more than
just a matter of performance.
Thanks,
Joseph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 20:37:21 2005