Tagging the current state, now that the initialization of the the new, public
repository is complete in the sense that it now has exactly the same contents
as the old repository that was previously used internally at CFS. That is:
svn checkout https://svn.lcube.de/dev123/projects new-repos -r 38
svn checkout svn://thubi-warrior/Projects old-repos -r 1097
yield working copies that have the exact same contents!
Use e.g. "Beyond Compare" for verification (set binary comparison mode and
exclude the ".svn" directories from the comparison).
To be perfectly honest and 100% correct, there are actually four exceptions:
There are four files in /tools in the old repository that are not in the new
one. This is intentional and the four files in question should actually be
deleted in the old repository soon, e.g. in r1097 (maybe they have already
been deleted when you read this).
Besides the files, even the Subversion properties are exactly the same:
svn proplist new-repos -v -R > new-props.txt
svn proplist old-repos -v -R > old-props.txt
yield exactly identical files, with minor exceptions related to the above four
files in /tools and the one svn:mergeinfo instance for /vendor/noise.
(Again use e.g. "Beyond Compare" for verification.)
git-svn-id: https://srv7.svn-repos.de/dev123/projects/cafu/tags/new-repository-init@39 5fe0b3f3-48df-4727-b460-e6dda9226989