Subversion for beginners brief Information


Published on

A brief information about usage of Subversion. SVN

Published in: Technology
1 Like
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Subversion for beginners brief Information

  1. 1. Subversion
  2. 2. What is Version Control? <ul><li>Normally when we save things we loose previous changes. </li></ul><ul><li>Lets se we have a file and has been edit many tings since its creation. </li></ul><ul><li>We cannot track of the changes done. </li></ul><ul><li>Version control track changes and adds a number to each changes called VERSION or REVISION. </li></ul><ul><li>Here nothing is lost. Its saved and be be retrieved anytime. </li></ul>
  3. 3. What is Subversion? <ul><li>It’s a free version control software. </li></ul><ul><li>In our case we user Tortoise SVN UI tool. </li></ul>
  4. 4. Terminology <ul><li>Repository </li></ul><ul><li>Check out </li></ul><ul><li>Working copy </li></ul><ul><li>Commits or check-in </li></ul><ul><li>Revert. </li></ul><ul><li>Updates. </li></ul><ul><li>Conflicts. </li></ul>
  5. 5. Repository <ul><li>Place where data is stored. </li></ul><ul><li>The repository is a central database of every version of every file. </li></ul><ul><li>Internally, they store deltas of each change which are not human editable. </li></ul>
  6. 6. Checkout <ul><li>To pull the data from repository to your local machine. </li></ul>
  7. 7. Working copy <ul><li>This is what comes out of the repository </li></ul><ul><li>It’s just a normal directory on your local machine. </li></ul><ul><li>All changes or edits are done here. </li></ul>
  8. 8. Commits or check-in <ul><li>Changes done in working copy remains locally until committed back to the repository or SVN. </li></ul><ul><li>Check ins saves your local copies or local changes into repository for ever. </li></ul><ul><li>Always add a log message while committing to track what changes were made in a particular commit. </li></ul><ul><li>Each commit creates a new version in repository. </li></ul><ul><li>I.e. new REVISION NUMBER. </li></ul>
  9. 9. Revert <ul><li>Removing the changes made locally and bringing back the file to the state as it was in repository. </li></ul><ul><li>Lets say we did some modifications on a file. And in many cases we mess up with it. </li></ul><ul><li>Now, we want to start from a fresh. </li></ul><ul><li>Reverting a file and do it again. </li></ul>
  10. 10. Updates. <ul><li>Synch your local working copies with the changes done on the repository by others. </li></ul><ul><li>Lets say some body modifies a file and have committed it in repository. </li></ul><ul><li>Updating working copy will bring those changes to you and keep it in synch. </li></ul>
  11. 11. Conflicts <ul><li>Nobody will every want to see this! </li></ul><ul><li>Lets say more then one person is working on a file. </li></ul><ul><li>Person A have done changes locally and committed it back to repository. </li></ul><ul><li>Mean while, Person B also did similar change. </li></ul><ul><li>Now before committing when Person B updates a local copy he gets conflicts. </li></ul><ul><li>Conflicts has to be resolved for your changes to be committed back. </li></ul>
  12. 12. Important notes. <ul><li>Always update your working copies regularly. </li></ul><ul><li>If more people are working on it then update daily or on hourly basis based on work. </li></ul><ul><li>Always add a log message while committing. </li></ul><ul><li>Update your local copy before starting working on it and before committing. </li></ul><ul><li>Its better not to check in half completed things which may break things for others. </li></ul><ul><li>Always see what files you are committing. Do not commit things which are not required. </li></ul>