to the server; users commit changes to the sever, checkout the latest revision from the server. • No direct exchange between developers Wednesday, April 25, 12
copy of repository is identical and self-sufficient • No need for a central server, but one may choose to have one • Developers may directly exchange changesets over Wi-Fi at a local coffee shop Wednesday, April 25, 12
Space efficient • Independent of network access or a central server • Superior branching and merging mechanism • Various protection devices against corruption Wednesday, April 25, 12
.edu email address • Since Git does not requires a central server, we can even work in an airplane • Slave-driver-type supervisors (e.g., Dr. Chiu) will love this • Given the nature of our development team, we can’t fully take advantage of all the benefits of Git, but we use it mainly for its speed and ease of branching and merging. Wednesday, April 25, 12
• Compiled binary, automatically generated code (e.g., R.java for Android) • Personal preference configuration files • .gitignore file contains a list of files that will be ignored by Git Wednesday, April 25, 12
a particular commit • Automatically updated whenever a commit is made to that branch • Tag marks a particular commit • May be moved manually Wednesday, April 25, 12
code when you are done <<<<<<< HEAD:file.txt Hello world ======= Goodbye >>>>>>> 77976da35a11db4580b80ae27e8d65caf5208086:file.txt Wednesday, April 25, 12