GIT Source Control System

A Short History of Git

10 Years of Git: An Interview with Git Creator Linus Torvalds

A year with Git

how to set up a centralized Git repository

Simple git server for Windows:

Git Stack – Git Server for Windows


git – the simple guide
“just a simple guide for getting started with git.”


3 Reasons to Switch to Git from Subversion
“1) Git creates a full repository with this command. With Subversion, you’re just checking out the files in the repository.
2) With each branch, no new files are created in the project file hierarchy on your system. Since you have a full local repository, Git creates the files you need on the fly by processing the recorded changes. With Subversion, you have to create every branch remotely on the server. This can get messy depending on the size of your team. If you decide to control branching to keep things clean, you forfeit the power branching offers.
3) With Git, we only push our work to the server AFTER collaboration (more below). With Subversion, it all hits the server.
4) Again, no file system work. Since we’re using a local repository, we let Git handle the details of removing the branch. With Subversion, you still have the old copy until you update. You either have to clean up manually, or “update” to clean up local and remote copies.”
Why You Should Switch from Subversion to Git
GitSvnComparison: A summary of differences
“Git is much faster than Subversion
Subversion allows you to check out just a subtree of a repository; Git requires you to clone the entire repository (including history) and create a working copy that mirrors at least a subset of the items under version control.
Git’s repositories are much smaller than Subversions (for the Mozilla project, 30x smaller)
Git was designed to be fully distributed from the start, allowing each developer to have full local control
Git branches are simpler and less resource heavy than Subversion’s
Git branches carry their entire history
Merging in Git does not require you to remember the revision you merged from (this benefit was obviated with the release of Subversion 1.5)
Git provides better auditing of branch and merge events
Git’s repo file formats are simple, so repair is easy and corruption is rare.
Backing up Subversion repositories centrally is potentially simpler – since you can choose to distributed folders within a repo in git
Git repository clones act as full repository backups
Subversion’s UI is more mature than Git’s
Walking through versions is simpler in Subversion because it uses sequential revision numbers (1,2,3,..); Git uses unpredictable SHA-1 hashes. Walking backwards in Git is easy using the “^” syntax, but there is no easy way to walk forward.”
“DVCS proponents point to several advantages of distributed version control systems over the traditional centralized model:
Allows users to work productively even when not connected to a network
Makes most operations much faster since no network is involved
Allows participation in projects without requiring permissions from project authorities, and thus arguably better fosters culture of meritocracy instead of requiring “committer” status
Allows private work, so users can use their revision control system even for early drafts they do not want to publish
Avoids relying on a single physical machine as a single point of failure.
Still permits centralized control of the “release version” of the project”


Please. Stop Using Git. – Matthew McCullough


Git Large File Storage