Introduction To GIT.pptVIP

Introduction To GIT Rob Di Marco Philly Linux Users Group July 14, 2008 A Brief History of Git Linus uses BitKeeper to manage Linux code Ran into BitKeeper licensing issue Liked functionality Looked at CVS as how not to do things April 5, 2005 - Linus sends out email showing first version June 15, 2005 - Git used for Linux version control Git is Not an SCM Never mind merging. Its not an SCM, its a distribution and archival mechanism. I bet you could make a reasonable SCM on top of it, though. Another way of looking at it is to say that its really a content-addressable filesystem, used to track directory trees. Linus Torvalds, 7 Apr 2005 /lkml/2005/4/8/9 Centralized Version Control Traditional version control system Server with database Clients have a working version Examples CVS Subversion Visual Source Safe Challenges Multi-developer conflicts Client/server communication Distributed Version Control Authoritative server by convention only Every working checkout is a repository Get version control even when detached Backups are trivial Other distributed systems include Mercurial BitKeeper Darcs Bazaar Git Advantages Resilience No one repository has more data than any other Speed Very fast operations compared to other VCS (I’m looking at you CVS and Subversion) Space Compression can be done across repository not just per file Minimizes local size as well as push/pull data transfers Simplicity Object model is very simple Large userbase with robust tools Some GIT Disadvantages Definite learning curve, especially for those used to centralized systems Can sometimes seem overwhelming to learn Documentation mostly through man pages Windows support can be an issue Can use through Cygwin Also have the msysgit project Git Architecture Index Stores information about current working directory and changes made to it Object Database Blobs (files) Stored in .git/objects Indexed by unique hash All files are stored as blobs Trees (directories) Commits One object for every comm