git | A fork of Git containing Windows-specific patches

git is a C library. git has no bugs, it has no vulnerabilities and it has medium support. However git has a Non-SPDX License. You can download it from GitHub.

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net. Please read the file [INSTALL][] for installation instructions. Many Git online resources are accessible from including full documentation and Git related tools. See [Documentation/gittutorial.txt][] to get started, then see [Documentation/giteveryday.txt][] for a useful minimum set of commands, and Documentation/git-.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git- or git help . CVS users may also want to read [Documentation/gitcvs-migration.txt][] (man gitcvs-migration or git help cvs-migration if git is installed). The user discussion and development of core Git take place on the Git mailing list — everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read [Documentation/SubmittingPatches][] for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at and other archival sites. The core git mailing list is plain text (no HTML!). Issues which are security relevant should be disclosed privately to the Git Security mailing list . The maintainer frequently sends the "What’s cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.