[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Branko ─îibej <brane_at_apache.org>
Date: Thu, 15 Mar 2018 21:37:45 +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? Files and directories exist on
Windows, too, it doesn't matter what the names are. If you can't
extrapolate instructions to your specific OS, you'll have no end of
trouble using any tool that works with files and directories ...

> that I
> lost track of how it could be done and then finding the other reply
> and looking up that led me to the procedure I showed.
> Also, I normally already have the files when subversion comes into
> play...

That does not matter. The point is that you check out an empty tree in
the repository over an existing tree in your local filesystem and that
will magically create a working copy with no versioned objects in it.

-- Brane
Received on 2018-03-15 21:38:53 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.