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

Re: Clueless beginner questions

From: Stefan K√ľng <tortoisesvn_at_gmail.com>
Date: 2007-08-31 22:31:30 CEST

novnov wrote:
> Actually, I don't know much of anything to do with this <g>. So I'm not sure
> what you mean by "Of course, you know that file:/// access doesn't have
> anything to do with your xampp installation?" I know svn is using apache,
> but I'm not sure what that's got to do with the path I feed the import
> command.

With a file:/// url, you access the repository directly. If you want
your repository served via apache, you would have to use a http:// or
https:// url to access the repository.
You really should read our docs, especially chapter 3 (setting up a server).

> I was able to import the files into the repository...but the naming seems
> backwards. If I'm in dir A and want to push files into B, I'd call it an
> export. If starting from B, and pulling from A, I'd call it an import. I've
> never seen the terms used as they are here but adapting is easy. Maybe it's
> an svn thing, not tortoise.

Yes, that's how Subversion names the commands. You *import* your files
into the repository, then you *checkout* those files again to get a
local working copy. *Export* means you get the files from either your
repository and export them to some location, without having them
assigned to the repository (i.e., the .svn folder is missing), or you
export a versioned working copy to a fresh location where the files are
not versioned anymore.
But this too is explained in full in our docs.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Aug 31 22:28:46 2007

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

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