Stefan Küng wrote:
> 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".
I mentioned in another e-mail that I found it. And, yes, it took 5+
hours to find it whether you believe me or not. "Daily Use Guide" is a
terrible description of the section. I assumed something by that name
would be for users who have already set everything up and are needing
more advanced features. So, I was spending the majority of the time in
the Appendecies because they had titles that seemed more relevant.
>> 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)
That's just the current layout on the hard drive. It isn't what I've
got set up in Subversion. I've got the recommended /trunk, /branches,
>> 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
> If you follow section 5.2.1 in our docs, you can read about branches and
I've read it and Appendix B. It didn't answer my question. There are
several methods discussed and none of them are indicated as the
"favored" or "preferred" method. And none really address my scenario.
I just tried the svn:externals approach and that creates a copy of
CoreLibrary in each project's directory. CoreLibrary is huge and I'd
prefer not having it duplicated everywhere, but what SVN is doing makes
_some_ sense at least for previous versions. For the current version,
however, it doesn't make much sense to have the same code duplicated
everywhere. I work on multiple projects and applications at any given
time that all rely on the CoreLibrary project. I don't want to have to
commit every change I make just to synchronize multiple copies. The
problem could be solved with allowing relative directories via '..', but
unfortunately svn:externals doesn't allow that.
>> IMO, information like this should be part of the documentation/FAQ.
> It is. It's called Daily-Use-Guide, and part of our docs.
Yeah, I found it after hunting for 5 hours. I still think it is named
improperly or the sections are organized incorrectly or something. I
generally don't read documentation in a linear order...just the parts
that seem like what I need.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Oct 1 16:58:18 2005