Version | Release Date |
---|---|
2.13 | May 10, 2017 |
2.12 | Feb 24, 2017 |
2.11 | Feb 02, 2017 |
2.11 | Nov 29, 2016 |
2.1 | Oct 28, 2016 |
2.1 | Sep 02, 2016 |
2.9 | Jun 13, 2016 |
2.8 | Mar 28, 2016 |
2.7 | Oct 04, 2015 |
2.6 | Sep 28, 2015 |
2.5 | Jul 27, 2015 |
2.4 | Apr 30, 2015 |
2.3 | Feb 05, 2015 |
2.2 | Nov 26, 2014 |
2.1 | Aug 16, 2014 |
2 | May 28, 2014 |
1.9 | Feb 14, 2014 |
1.8 | May 24, 2013 |
1.8 | Oct 21, 2012 |
1.7 | Apr 06, 2012 |
1.7 | Feb 13, 2010 |
1.6 | Oct 10, 2009 |
1.6 | May 07, 2009 |
1.6 | Aug 17, 2008 |
1.5 | Sep 02, 2007 |
1.5 | Feb 14, 2007 |
1.4 | Jun 10, 2006 |
1.3 | Apr 18, 2006 |
1.2 | Feb 12, 2006 |
1.1 | Jan 08, 2006 |
1 | Dec 21, 2005 |
0.99 | Jul 11, 2005 |
Git is a free, distributed version control system designed for tracking code changes through "snapshots" (commits). Commits, stored in a Git Repository, enable collaborative testing, debugging, and feature development. Repositories can be hosted locally, on private servers, or on open-source platforms like GitHub.
Git facilitates the creation of code branches, allowing different versions to coexist. This enables scenarios such as a stable version, a branch with new features, and another with different features. Creating and merging branches in Git is a seamless process.
Originally developed for managing the Linux kernel source, Git encourages small commits, project forking, and branch merging. Noteworthy changes from traditional systems like CVS or Subversion include the inclusion of the entire project history in each checkout.
Common operations such as diffing, checking out older revisions, committing locally, creating branches, and merging can be done without communication with a central server. Interactions with the "upstream" repository are mainly for syncing changes. This organizational flexibility contrasts with the technical constraint of traditional ownership.
By making local operations efficient, Git empowers developers with more control over project history and collaborative workflows.