Roberto Nucera wrote:
>Toby, Sean
>
>Thanks!!
>
>My final question...
>The document speaks of trees...? "Revision numbers apply to entire trees"
>
>What is a tree? For example is the entire repository the tree (repo =
>tree) or can there be somehow independent trees inside a repository.
>
>Toby, you say "trunk" and "branches" don't really fit our model of
>workflow, so we don't even use them.
>
>
Yes, the repository is the tree. A tree is just a handy metaphor. Your
repository and all of its version history can be thought of as a bunch
of trees planted in a row. The first tree is tree #0 and the last one is
the HEAD. Any time any part (or parts) of the tree changes, you get a
new tree. Most items will not change from one tree to the next. And any
given working copy can have multiple pieces from multiple trees within
it, until you "svn update".
My comment about trunk and branches not fitting our workflow is due to
the fact that we used to use VSS and had internal build and deployment
tools which required items to be in specific locations within the
repository. When we converted to Subversion, I left that structure
alone. The great thing about it is that Subversion doesn't even care. It
doesn't matter that I have no directory called "trunk" or "branches" or
"tags".
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 30 22:48:37 2005