One of the benefits of Trac is that it doesn't care
what our software is or what we are using to develop it. The only thing that matters
is that the code is stored in a Version Control System??”specifically Subversion.
You say to-mato, I say tom-ato...
When reading about Subversion we will see that it is often interchanged
with svn, which is the command we run to use it. We should feel free to
use the pronunciation we are most comfortable with??”anyone else who
uses it should recognize and acknowledge both.
We will cover what you need to know for using the system and processes described
in this title and then move on to branching and merging??”techniques that allow us to
isolate our changes during development.
Check Out, Check In
In Chapter 3 we set up our Subversion repository. This currently exists only on our
project server. Although we can perform some basic actions directly on this (as we
will see shortly), to actually use Subversion we need to have a working copy of this
on our client machine. We can get this working copy by performing an action known
as checking out. Once we have made some changes to our working copy we will
check them in to the repository. Until we check in our changes they are not a part of
the version history in our repository.
Pages:
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85