On 2/4/07, Richard Shea <rshea@thecubagroup.com> wrote:
> Hi - For some time now we've been producing directories of source which
> reflect our application at different stages ('3.1','3.2','3.3' etc - a
> sort of 'poor mans source control system').
>
> We've now setup svn and as a starting point would like to bring each of
> these version under source control so that we can look back through
> those version as well as all subsquent changes we make.
>
> This is more difficult than I had thought it would be. I can 'import'
> the first directory in the new repo but the next directory cannot be
> imported (by TortoiseSVN anyway) because there's already stuff in the
> repo. I then went through a process of : importing 3.1, checking out
> 3.1, deleting all files in working copy other than .svn's, copy 3.2 into
> working copy area and checking in (and so on for 3.3,3,4 etc). However
> this process seems to have missed out the new files.
>
> I think I know what I did wrong but is there a better way ?
If you want to have a history of the changes from version to version
easily maintained, I'd say you did everything right, with one
exception. You need to add those new files, and delete any that appear
in version X that don't appear in version X+1. Subversion only
"missed" those files because you didn't tell it they needed to be
versioned.
The svn-load-dirs.pl script may be of value to you, but I've never
used it so I don't know for sure.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 5 02:32:17 2007