anchor.diff:  
   == 3. Working with git
   
  -NOTE: You all should get a github ID. If you are working in teams, you have the option of either doing the next section individually, or choosing 1 team member to drive.
  +Git is a popular version control system used by software developers and DevOps professionals. One of the key characteristics that sets Git apart from many other version control systems is its distributed nature. Git scales easily from small projects involving a single person all the way up to projects involving a cast of thousands.
  +
  +We will work with a commercial implementation of the Git platform in this class provided by Github. You can create a free account on Github and host public code repositories, like the one we setup for this lab.
  +
  +NOTE: Everyone should setup an individual Github account. If you are working in teams, you have the option of either doing the next section individually, or choosing one team member to perform the git forking and cloning tasks.
   
   You will do the exercises in part 2 on the main server, not your VM (which you have now destroyed, right?).
   
  
positive.code: 
  Re-commit your Vagrantfile and push it back to origin.
  
  Issue a pull request for me to review your work.
  
  Discuss:
  
  - Why can you commit to git on the VM without initializing the repo there? You had to at least set up your name and email.
  - How are git and tree getting installed, since you don't say "sudo vagrant up"?
  
  That is the end of this lab. Congratulations, this was a lot of work. Next week, we will start working on the the continuous integration pipeline with git, Java, JUnit, Tomcat, and Ant.
  
negative.code: To https://github.com/YourGithubIDYourGithubID/example.git
     1c23c80..72958e4  master -> master
  ....
  Note, your script is at risk until you do this because your script only exists on your local hard drive. Pushing your repository up to Github is like making a backup copy of your source files.
  
  Exit the Vagrant instance (now back on the class server prompt) and destroy your Vagrant virtual machine:
  
      vagrant@vagrant:/vagrant$ exit
  	logout
  	Connection to 127.0.0.1 closed.
  	YourStudentID@serverXXX:~/example$ vagrant destroy
  
  Notice that your script is still in your ~/example directory. Again, all files in the /vagrant directory on your virtual machine were mapped to the ~/example directory on the host server.
  
  ....
  YourStudentID@serverXXX:~/example$ cat YourStudentID-Lab02.sh
  