Thomas Hruska wrote:
> 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?
Just read the next chapter in our docs (the one after
3.Setting-up-a-server and 4.The-repository: 5.Daily-Use-Guide).
There the first sections are called "Getting Started", and most
important for you: "Importing Data Into A Repository".
> Once I've got my content added to the repository, what should I do with
> the original data?
As our docs tell you:
- check out a working copy
- if your very paranoid, compare the working copy with your original data
- remove the original data
> Also, my directory structure looks like:
You should really first read the docs before you start working on a real
project. Or at least first set up a playground repository where you can
learn the do's and don'ts of Subversion.
That directory structure isn't good. You should follow the Subversion
recommendations on how to structure the repository layout.
(Section 5.2.1 in our docs)
> 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?
If you follow section 5.2.1 in our docs, you can read about branches and
> 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?
That question really tells us that you haven't read anything about how
Subversion works at all (and this after you've searched the docs for 5
hours? I really doubt that!). You don't have to "check out" every file
you want to edit. Subversion uses the copy-modify-merge model, not the
lock-mofify-unlock model. So you can edit any file you want, without
having to "check out" it first (btw: checkout is used differently in
Subversion, it's not the same as a VSS checkout!).
Only if you set the svn:needs-lock property on all files, you first have
to lock files you want to edit, and unlock them after editing. But you
should do that only for binary files which can't be merged.
> 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.
It is. It's called Daily-Use-Guide, and part of our docs.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Oct 1 14:18:30 2005