RE: RE: Re: Why have a trunk dir, anyway?!

Quoting "Irvine, Chuck R [EQ]" <Chuck.R.Irvine@Embarq.com>:

> The new approach is like this:
>
>
> R1-----------------------
> \
> \
> \
> R2 \------------------------
> \
> \
> \
> R3 \------------------------
> \
> \
> \
> R4 \------------------------
>
> Horizontal lines are branches. There is not trunk in the sense that
> every development stream (dir) is treated exactly the same.

I'm not sure every stream is treated exactly the same _all the time_.
As someone else illustrated with pipes in an earlier message, there is
still an implicit trunk. Take R3 for example, it has to be treated
differently depending on which point you are on R3. If you are
somewhere on the "trunk", i.e., one of the backslashes above, it's the
same just-code-away as in the classical trunk approach. As soon as R4
is created, the dashes portion of R3 becomes effectively a branch,
where you have to remember to merge changes into R4.

-- 
JX
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org