ini.default
$ svn commit -m "Added .default config file." C
Adding application/configuration/config.ini.default
Transmitting file data ......
Committed revision 3.
A The status command gives feedback on the status of the working copy. In this case it points out that config.ini.default is not under
version control
B The file is added putting it under version control indicated by the A after a second status check
C Once the working copy is ready it is commited to the repository
In the code in listing 10.6 you may have noticed the repeated status checks. To be sure that your working
copy is as you expect it's a good idea to get into the habit of checking its status before performing any further
action.Updating a local working copy
At each stage of development we need to be checking on the status of our working copy and making sure that
it is up to date with the repository. Not surprisingly, the svn update command takes care of updating a local
working copy with the latest changes and those changes are indicated by the output of the command. In listing
10.7 we perform an update on our working copy.
Listing 10.7 Updating our working copy from the repository
$ cd ~/Sites/places
$ svn status A
$ svn update B
A application/classes
A application/classes/Places
A application/classes/Places/Controller
A application/classes/Places/Controller/Action
A application/classes/Places/Controller/Action/Helper
A application/classes/Places/Controller/Action/Helper/ViewRenderer.
Pages:
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289