Stefan Sperling <s...@elego.de> writes: > Yes. And if the content differs, it must be rejected, because an FSFS > repository can only store one content per SHA1 checksum.
To be accurate the server-side code can handle the files perfectly well if rep-caching is disabled. One can retreive either file, dump/load into another repository, etc. # Import 2 files from shattered.io svnadmin create repo1 echo [rep-sharing] >> repo1/db/fsfs.conf echo enable-rep-sharing=false >> repo1/db/fsfs.conf svn import -mm shattered-1.pdf file://`pwd`/repo1/f svn import -mm shattered-2.pdf file://`pwd`/repo1/g # dump/load svnadmin create repo2 echo [rep-sharing] >> repo2/db/fsfs.conf echo enable-rep-sharing=false >> repo2/db/fsfs.conf svnadmin dump repo1 | svnadmin load repo2 # verify files have same SHA1 but different MD5 $ svnlook cat repo2 f | sha1sum 38762cf7f55934b34d179ae6a4c80cadccbb7f0a - $ svnlook cat repo2 g | sha1sum 38762cf7f55934b34d179ae6a4c80cadccbb7f0a - $ svnlook cat repo2 f | md5sum ee4aa52b139d925f8d8884402b0a750c - $ svnlook cat repo2 g | md5sum 5bd9d8cabc46041579a311230539b8d1 - The on the client side the working copy code doesn't handle the files as the pristines collide. -- Philip
