Re: Can import also convert the source to a working copy

2018-03-15 Thread Daniel Shahaf
Branko Čibej wrote on Thu, 15 Mar 2018 21:37 +0100: > On 15.03.2018 20:18, Bo Berglund wrote: > > On Thu, 15 Mar 2018 13:45:13 -0400, Kris Deugau > > wrote: > > > >> Unless I misread your original post, the very first option in that link > >> looks like a better fit. To rephrase it somewhat for

Re: Can import also convert the source to a working copy

2018-03-15 Thread Branko Čibej
On 15.03.2018 20:18, Bo Berglund wrote: > On Thu, 15 Mar 2018 13:45:13 -0400, Kris Deugau > wrote: > >> Unless I misread your original post, the very first option in that link >> looks like a better fit. To rephrase it somewhat for your case: >> >> 1) Create a repository or a directory in the r

Re: Can import also convert the source to a working copy

2018-03-15 Thread Bo Berglund
On Thu, 15 Mar 2018 13:45:13 -0400, Kris Deugau wrote: >Unless I misread your original post, the very first option in that link >looks like a better fit. To rephrase it somewhat for your case: > >1) Create a repository or a directory in the repository >2) Create your local files >3) Check ou

Re: Can import also convert the source to a working copy

2018-03-15 Thread Kris Deugau
Bo Berglund wrote: On Thu, 15 Mar 2018 12:03:53 +0100, Johan Corveleyn wrote: See http://subversion.apache.org/faq.html#in-place-import Seems like the best option is as follows: - svn import WiFiConfig /WiFiConfig/trunk --depth files -m "msg" svn co W

Re: Can import also convert the source to a working copy

2018-03-15 Thread Bo Berglund
On Thu, 15 Mar 2018 12:03:53 +0100, Johan Corveleyn wrote: >> Is there some flag or such that can help out during the import or in a >> following checkout so that the extra directory >something else> does >> not need to be used? >> >> Or can I just move the .svn dir from the working copy to the o

Re: Can import also convert the source to a working copy

2018-03-15 Thread Branko Čibej
On 15.03.2018 11:48, Bo Berglund wrote: > I have used this sequence for handling new projects with svn: > > - Start a new project in whatever IDE is used > - Work a bit on initial code so the framework is OK > - Exit the IDE > - Command prompt in the parent of the project dir > - svn import --dep

Re: Can import also convert the source to a working copy

2018-03-15 Thread Johan Corveleyn
On Thu, Mar 15, 2018 at 11:48 AM, Bo Berglund wrote: > I have used this sequence for handling new projects with svn: > > - Start a new project in whatever IDE is used > - Work a bit on initial code so the framework is OK > - Exit the IDE > - Command prompt in the parent of the project dir > - svn

Can import also convert the source to a working copy

2018-03-15 Thread Bo Berglund
I have used this sequence for handling new projects with svn: - Start a new project in whatever IDE is used - Work a bit on initial code so the framework is OK - Exit the IDE - Command prompt in the parent of the project dir - svn import --depth files -m "message" - rename - svn co - move \