Demo one: Getting started

Let's take a look at Version Control in action.…First, we'll look at it conceptually, and then we'll actually do it.…So in this diagram, the repository where your files are kept is represented by the large…right-facing arrow and contains the different versions of our files over time.…So at 9 a.m., you create a repository for your new project.…This creates the empty database to which you can add files to be tracked.…Oftentimes this is done by a command called Init.…At 10 o'clock you create myprog.c and add just the main function.…

Then you add it to your repository by checking it in. With each add or check in, Version Control…systems ask you to compose a short message indicating why you are performing the check in.…In this case, we'll say add myprog.c.…Later on at 4 o'clock, you edit myprog.c again and add Func1 and save it back to your hard disk.…This updates your working set, making it different from now what's stored in your repository,…so you check in again.…Now your repository has two versions of your file and two commit messages.…