On Feb 4, 2007, at 23:22, Richard Shea 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 ?
>
> Thanks for all for the replies and the sample code. The server in
> question doesn't have Perl installed (it's W2003 - so no csh
> either) but I was able take your ideas and cobble together
> something in Python. I've attached the source to this email
> although it required me to do some fiddling with the output in Vim
> I still thought it might be a useful starting place for someone
> else in the same situation who was Python inclined. Thanks again
> for your help.
I'm glad you got it worked out, but for future reference, you needn't
run svn_load_dirs.pl on the server machine; you can run it on any
client, for example a Linux or Mac OS X machine where Perl will
already be installed.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 5 09:51:03 2007