Committing To The RepositoryCommitting to the repository allows developers to upload the changes they have made in their working directory back to the development server. This allows collaboration with other developers where others can download the updates made and help finalize the work involved. Each developer that has an account to commit to the repository has their own copy of /trunk/ in the /branches/ directory. This allows developers to work on their own version in their branch to not interfere with what has been worked on in the /trunk/ directory. When the work has been finalized in the developers branch it is then copied over to the /trunk/ directory where it is then available for the next project release made. Each commit made to the repository attaches the developers name and a description of the changes to the changes made. This allows each commit and change to be stored in the repository database where it can be referenced to. For the following status report, a new file will also be added to the repository to group the related changes into one commit: ? admin/includes/classes/image.php ? admin/includes/classes/database.php M admin/products.php M admin/templates/pages/products_edit.php ? images/products M install/oscommerce_sample_data.sql M install/oscommerce.sql svn add admin/includes/classes/image.php svn commit admin/includes/classes/image.php admin/products.php \ admin/templates/pages/products_edit.php install/oscommerce.sql \ install/oscommerce_sample_data.sql By specifying the filenames to the commit command only those files will be included in the commit that is made. If no filenames were directly specified, subversion will commit all modified files recursively.
Please refer to the Commit Policy to find out the procedures of committing changes to the development server. |
