add: if we have created a new file that is not on the server, you use add to tell SVN to upload it to the remote server on the next commit.diff: this checks our local file(s) and those on the remote server for differences.co: check out, this downloads the current or highest revision from the repository to our local machine.So now that we have established what version control is, how do we use it? For basic operation there are only a few command we really need to know: We are able to revert to that older file, but also have the newer file that might contain other bits that were changed that are still valid, at our fingertips. In our case we actually wanted that "p" to be a "p", not a "q". Version Control allows you to fall back to an older version of a file if needed. This does not destroy your previous file, it merely adds a new "version" of that file. In essence you change a "p" to a "q" in your file and upload that to your server, your revision control system will identify that there is a change and create a new "revision". Version control allows you to maintain multiple versions of a file.
This could be HTML and PHP files, or C++. In short revision control breaks down like this:Ī central location to house your source code. That is a valid question, and one that I get pretty often when I am talking about CVS, SVN or Arch.
This little ditty will assume that you have an SVN repository to connect to already, and all you need is the client-side tools. So you want to get Subversion running on your mac, complete with nifty finder integration? Good, welcome to the wonderful world of revision control.