Can import also convert the source to a working copy

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 \

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

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

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

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

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

unsubscribe

Kind Regards / Med venlig hilsen Lars Nielsen

RE: unsubscribe

> -Original Message- > From: Lars Nielsen [mailto:l...@lfweb.dk] > Sent: Thursday, March 15, 2018 2:33 PM > To: users@subversion.apache.org > Subject: unsubscribe > > > Kind Regards / Med venlig hilsen > > Lars Nielsen Hi Lars, Instructions are here:- https://subversion.apache.org/mail

Actual checksum is always different

Hello, OS: Ubuntu Server Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64) Server Software: svn --version svn, version 1.9.3 (r1718519) - this is the latest version available on Ubuntu servers Cliet OS: Windows 10 Pro (latest updates) Client Software: TortoiseSVN 1.9.727907 64-bit *Issue

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

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

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

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: E130003: The XML response contains invalid XML - Follow-up

Folks, I used dump and load to debug the malformed node revision ID. Here are my steps and what learned. Looks like the revs' file text: entry has a zero instead of size. By just editing the size, verify worked. No other change was required. The question is can we correct this ourselve

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

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