[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

'importing' prevous manual source control system - go to be a better way ?

From: Richard Shea <rshea_at_thecubagroup.com>
Date: 2007-02-05 02:17:56 CET

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

Richard.

 

---------------------------------------------------------------------
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:18:27 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.