zend.com/svn/framework/trunk/library/Zend/
Now any checkout of the repository that includes that local directory will also will also checkout the Zend
Framework code.
10.2.3 Branches
We gave an example of how tagging could be used for marking the repository at specific points in the
progress of the chapters of this book but what about a bigger occasion such as when we actually finish it? That
would be an occasion to use the branching capabilities of Subversion:
$ svn copy http://www.example.com/svn/places/trunk/ \
http://svn.example.com/places/branches/its-finished \
-m "Woohoo, we've finished the book!"
Committed revision 200.
As the name suggests and figure 10.3 illustrates, branching creates a line of history independent of the
main trunk. There are numerous reasons why we may decide to branch our code, Zend Framework branches on
each official release, but we could as equally decide to branch based on a need for a custom version of the
main code or an experimental version.
Licensed to Menshu You
Zend Framework in Action (Ch01) Manning Publications Co. 10
Figure 10.3 Branches in an SVN repository
The subject of branching is the topic of a whole chapter into itself so this brief mention is really just to
indicate its use and hope that you the reader follow it up with your own research.
Pages:
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294