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

[TSVN] Created a repository...now what?

From: Thomas Hruska <thruska_at_cubiclesoft.com>
Date: 2005-10-01 08:06:40 CEST

The documentation and FAQ are basically non-existent in this (at least I
couldn't find anything after searching for 5 hours). I have a very
large, already existing code base and wish to start using Subversion via
TortoiseSVN. I followed the directions to create a repository, but
obviously it is empty. How do I get my existing content into the brand
new repository given that I have no existing repository except for files
on the hard drive?

Once I've got my content added to the repository, what should I do with
the original data?

Also, my directory structure looks like:


What is the _preferred_ method of making sure that previous versions of
Project1 and Project2 stay synchronized with previous versions of
CoreLibrary _BUT_ the latest versions of both projects (and all
subprojects) use the latest version of CoreLibrary? Assume CoreLibrary
is a 500MB hosebeast. How do I set this scenario up via TortoiseSVN?

Then, how do I go about using the repository from within, say, Visual
Studio? Do I have to locate the file on the hard drive and check it out
first OR can I simply start editing? Or do I have to use some user
interface other than the shell to check files out?

Basically, I'm looking for step-by-step guidance. Right-click here,
click this button, select this file, etc. Assume that I've never used
any version control software before. (I used SourceSafe once upon a
time, but it has been a while).

IMO, information like this should be part of the documentation/FAQ.

Thomas Hruska
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Oct 1 08:07:09 2005

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

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