On 31/08/2007, novnov <novnovice@...> 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
SVN can use three different methods to serve repositories: apache,
svnserve or local file access. The way you select is with the protocol
part of the URL. If you specify file:/// then you are using local file
access (TortoiseSVN acts as both client and server). You may have
xampp installed, but in this case it is not being used.
> 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.
That's just the convention used - it works from the repository's point
of view. The act of creating a new local working copy is called
Checkout, and updating that working copy is called Update. You
*really* need to read the docs.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net