Matthias Schniedermeyer <matthias.schniedermeyer@mediaways.net> writes:
> - cut -
> cp -al <rep-dir> <rep-dir-copy> # Copy all files using hard-links
> cd <rep-dir>
> svn up
> cd ..
> diff -Nur --exclude=.svn <rep-dir-copy> <rep-dir>
> - cut -
>
> failes to see any differences. Seems linke the file(s) (is/are)
> overridden instead of replaced. (The "new"-file(s) (has/have) the
> same inode as the "old"-file(s).) CVS does this right(tm), it
> creates (a) new file(s) when you update/checkout from the
> repository.
>
> In my eyes this is a serious flaw.
If a file has changed on the server, svn simply applies a patch to the
working copy file, in-place, using diff3. That's how it preserves
local modifications. I guess we could make this more complex... make
a tmp copy of the working file, patch it, delete the original, copy
the tmp file back?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 7 16:20:02 2002