In the first installment, I showed how basic usage of git does not need any concept that is unique to a particular version control system. In this installment, I'll introduce more usage of git that requires learning a concept or two.
More and more projects are switching over to git or other distributed VCS. Even projects using centralized servers are doing so, because even if your project doesn't have a network of developers each with their own repository, distributed VCS have a very nice set of additional features. For example, the set of available offline operations is very complete; and as a consequence, not relying on network connection makes the system much faster even when you are not offline. Also, the possibility to quickly create and throw away branches makes it easier to do experiments.