Introduction to Git

EmSys:Git - Why have source code managementEmSys:Git - ProblemEmSys:Git - ApproachesEmSys:Git - The preferred solutionEmSys:Git - How it worksEmSys:Git - Reasons to Use Version Control SystemEmSys:Git - Our AimEmSys:Git - A Brief History of GitEmSys:Git - Git is Not an SCMEmSys:Git - ConceptsEmSys:Git - Centralized Version ControlEmSys:Git - Distributed Version ControlEmSys:Git - AdvantagesEmSys:Git - DisadvantagesEmSys:Git - ArchitectureEmSys:Git - VocabularyEmSys:Git - Key Files and DirectoriesEmSys:Git - Three StatesEmSys:Git - File Status LifcycleEmSys:Git - How to get gitEmSys:Git - First-Time Git SetupEmSys:Git - First-Time Git Setup2EmSys:Git - Ignoring FilesEmSys:Git - Basic WorkflowEmSys:Git - Initializing a RepositoryEmSys:Git - Our First RepositoryEmSys:Git - Working With GitEmSys:Git - Viewing What Has ChangedEmSys:Git - Git and Patch filesEMSys:Git - Undoing What is DoneEmSys:Git - Git and TaggingEmSys:Git - BranchingEmSys:Git - Using BranchesEmSys:Git - Using RemoteEmSys:Git - Cloning our RepositoryEmSys:Git - Cleaning Up Introduction to Git EmSys:Git - Why have source code management Slide 1 of 36

Why have source code management? Document state of a system and rationale for changes Coordinate simultaneous deployment of multiple changes to complex systems Allow reversion to previous versions in case of problems Ease sharing code on multi-developer projects Facilitate code audits Speed system re-creation