On Jun 10, 2010, at 17:24, Lieven Govaerts wrote: >>> Is the SVN server smart enough to realize that, even if I follow this >>> course of action, that >>> >>> /trunk/foo/bar.c >>> /tags/release1/foo/bar.c >>> /tags/release2/foo/bar.c >>> >>> are all the same file with minor (if any) differences? >> >> If you do this you are going to get several copies. >> >> What I would do is create a trunk and import the oldest ZIP that you have. >> Then get a check out of trunk and copy your next version over it. Do and >> "add" and "commit" then tag it. Continue. >> >> Actually, there is a utility that is designed to import ZIPs that are >> different versions. Although now that everything is at apache.org I don't >> know where to find all the little utilties that used to be on tigris.org... >> and they don't seem to be at tigris.org either. >> > > All files from svn.collab.net have been copied to svn.apache.org. > You're probably talking about svn_load_dirs.pl, which is the tool that > the documentation refers to in the 'vendor drop' chapter. You can find > it here: > http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svn_load_dirs/
Yes, svn_load_dirs.pl is exactly the script you want for this scenario. It's how I initially imported my make-a-copy-every-so-often pseudo-version-control into Subversion years ago.
