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

RE: Dumb question, perhaps

From: <jason_at_subversus.org>
Date: 2006-06-28 18:56:03 CEST

Well, the best way to imagine SVN is that of a database. If you've ever
used a database, you realize that it's something of a black box. Stuff goes
in, stuff comes out, but how it's stored on your hard drive is of no real
concern to you. It does what it's supposed to do, and shields you from the
gory details of the data. SVN is no different. You access SVN through your
client software, but you NEVER touch your repository directory or files
(except in extreme circumstances, but that's a side point).


The big problem here is that you've created folders within your database
(trunk, branches, tags). That would be like opening your database file in a
hex editor and flipping bits. Instead, you need to access your repository
through the client (TSVN). If you want to make changes, you either do it
through the repo browser, or you check out a working copy from your
repository (in a directory SEPARATE from your repository directory), make
changes within that working copy, and then commit them back to the


You don't really need to worry about where and how the data is stored.
Subversion takes care of those details for you. (It does so BTW, for the
curious, in the 'db' directory that was auto-created). Subversion also
takes care of what you refer to as the "link between the files" you
originally imported. If you take a look in the 'db' directory, you will see
a series of files which is essentially your database.


As for deleting the trunk, branches, and tags directories that you created
manually, well, there shouldn't be anything in those. And in that case,
yes, you can delete them.


It sounds a bit as though you haven't read the manuals. Which in case, you
should do so.


Generic Subversion book: http://svnbook.red-bean.com/

TSVN documentation: http://tortoisesvn.sourceforge.net/?q=support



From: Kevin Perese [mailto:kevin.perese@gmail.com]
Sent: Wednesday, June 28, 2006 12:12 PM
To: users@tortoisesvn.tigris.org
Subject: Dumb question, perhaps



I'm a complete novice to svn, tortoisesvn, and version control in general so
I apologize if these questions are dumb. I work on a project that could
really benefit from some version control software and svn and tortoisesvn
seem to be great candidates. I've recently started learning how to use
tortoisesvn and getting my feet wet with it before pitching it to my boss
for our entire project. So my game plan was to not install a server
anywhere, but to just install the client and start working with a local
repository for my own small projects to learn the ropes. So far, so good, I

I've followed the directions for creating a local repository and importing
files to the repository. Upon creating a repository, there were several
file directories created (conf, dav, db, hooks, and locks) and I have no
idea what these are. I then created 3 more directories (trunk, branches,
and tags) as instructed in the manual. I had a parent directory for a
project (with several subdirectories and many subroutine files) that I then
imported to the trunk directory in the repository.

I've been able to check code out of the repository to a working directory,
make changes, commit these changes, and review differences, etc. -- all the
great tools that svn offers.

But what confuses me is how all the files are stored in the repository.
When I check the trunk directory in the repository, it's empty. Where and
how are the data stored? Is there still a link between the files I
originally imported to the repository? Can I delete the original source
directory that I imported to the repository? Is the repo-browser the only
way to view the repository contents? What is the repo-browser viewing?

I appreciate any elucidation anyone might be able to provide.

Received on Wed Jun 28 18:57:14 2006

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.