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 <kdeugau_at_vianet.ca>
> > 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 out the empty repository path to your workspace - this won't
> >> overwrite any of your files
> >> 4) svn add [files]
> >> 5) svn ci
> >> 6) Continue working as usual
> >>
> >> This avoids a round trip to the server to push the current files, then
> >> pull them back down to create the formal SVN working copy with things
> >> already in it - instead you "check out" an empty directory which should
> >> be quite fast.
> >>
> > I readthat page as best I could but it looked so much Linuxish
>
> What on earth is Linuxish about it?
You don't have to use the 'svn' client; you can use any Subversion
client (a GUI client, TortoiseSVN, IDE integrations...).
The docs always use the 'svn' client because (1) it's the only non-third-
party client, (2) it's a command-line client so it's easier to give
instructions for it.
Received on 2018-03-16 07:54:54 CET