Hi, Andreas, Von: Andreas Krey [mailto:a.k...@gmx.de] > On Mon, 22 Aug 2011 18:01:34 +0000, Markus Schaber wrote: > .... > > > What does not work that worked with 1.6? > > > > Those steps work nice, but they leave us with a working copy having > > the parent of the project directory as its root, instead of the > > project directory itself. > > Is there a reason that you can't do your import directly in the project > directory, and is it prohibitive to just 'svn up' and throw away the temp > dir instead of moving the tree into the project dir?
I cannot create a working copy directly in the project directory when the project directory is just to be created with the import. This is why we currently need an extra commit to create the project directory, as I described it in my sequence of steps for SVN 1.7. What exactly do you mean with "svn up" in this context? Best regards Markus Schaber ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.scha...@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
