Just think of the other members of your team having to check
out one big commit that includes a multitude of scattered changes and you quickly understand what that
means. You'll also notice any lack of focus when your commit messages start becoming unclear and difficult to
write. Whether formal or informal, most teams will have some commit guidelines such as including issue
tracker reference numbers in the commit message for example.
Going through our new working copy the first thing we notice is the need to edit the config.ini file to use
our local database. For now we can just make a copy which we call config.ini.default and use the original to
get the local application working. Ultimately we'll set the config file up more consistently but for now let's
commit config.ini.default as shown in listing 10.6, so that any further commits won't be writing over our
individual config files.
Listing 10.6 Committing our changes to the repository
$ cd ~/Sites/places
$ svn status | A
? application/configuration/config.ini.default A
Licensed to Menshu You
Zend Framework in Action (Ch01) Manning Publications Co. 7
$ svn add application/configuration/config.ini.default B
A application/configuration/config.ini.default
$ svn status
A application/configuration/config.
Pages:
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288