2010/10/5 Ryan Schmidt <subversion-20...@ryandesign.com>: > > On Oct 5, 2010, at 15:22, Tech Geek wrote: > >> and load project a as project b and take all the history with you. >> Just create a new project b without adding trunk etc. in revision 1. >> I do not want all the revision history of projectA into projectB. I just >> need to start projectB with the latest code (trunk HEAD of) projectA. >> >> May be I am missing something very obvious here... > > If you do not want to preserve the history, then you want to "svn export" > from the old repository and "svn import" it into the new repository.
You'll also want to seriously review the Subversion properties of the material before the export, in order to replicate them in the imported or "added" material. svn:externals, svn:keywords, svn:eol, etc., etc., etc. are not contained in an export: they're meta data in the Subversion repository, not the raw or even processed content of the exported files. This includes svn:eol, svn:keywords, and in particular svn:external. svn:keywords in particular, will create fascinating and confusing content in the keywords of the files at the time of your original import, so this is something to do cautiously. This is one of those cases where a bit of extra attention, instead of "just export it and import it" can save you some surprises down the road.
