[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Branches and tags

From: Paul Wayper <paul.wayper_at_anu.edu.au>
Date: 2005-06-03 03:42:44 CEST

Greg Matheson wrote:

>Perhaps I'm the same :-) I had the same experience reading the
>book. Being told about subversion and version control is
>different than using subversion to realize your own goals.
>
>It is like the difference between reading a foreign language grammar
>textbook and learning the language.
>
>
Having had to learn Subversion recently, I can relate to this. I would
add that one way that the book could be improved in this regard is to
have one or two examples that are consistently pursued through the
book. For instance, having the example of a calculator program, and
using the example of the writing of the Subversion book, would be
developed and expanded over the course of the book. This means that the
reader can absorb the detail about the example gradually, rather than
having to intuit a lot about the current example from context.

Which probably means that I should create a new branch of the book from
the Subversion trunk, and submit some updates that could later be merged
in. This would probably teach me more about doing this sort of thing,
as I've only done this once on my own projects. :-)

Ultimately, I think the book already states that you really need to use
it to be familiar with it, and that that branches, trunks and tags are
good practice that the reader might want to adopt even if e can't see
the point in it now.

Have fun,

Paul

-- 
-- Paul Wayper at ANU - +61 2 6125 0643
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 3 03:44:33 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.