> > I phrased that poorly. When I read the Introduction, I was under the
> > impression the recommended structure was as above; reading Chapter 3
> > changed my mind.
>
> Yah, as you'll see in chapter 5, the convention is to create what we
> call a "project root":
Whoa! Not so fast, I just finished Chapter 3! :-)
Seriously, I'll probably be rereading Chapter 3 again over the weekend and
experimenting based on my new-found understanding. I really *am* slow at
picking this stuff up sometimes, so it helps to reiterate through it.
> project/trunk
> project/branches
> project/tags
>
> The thing is, it's up to you to decide where the "root" is. If your
And that's why I was confused. Your structure above makes much more sense
to me, and my incomplete understanding of the structure presented by the
Introduction example was getting in the way of learning about SVN. Now that
I'm past it, hopefully it will go faster.
Brad
> repository only contains one project, it could be the "/" dir of the
> repository. (That's what the chapter 1 demo is doing.) If your
> repository has lots of projects, then project-roots could be scattered
> all over the place within it.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 19 21:23:45 2004