Devotd Github
NewDeveloper tools

git/git — Official source mirror and patch submission path

git/git is the official source mirror of Git, a repository where the implementation of the version control system and the patch submission procedure can be checked.

Repositorygit/git ↗

git/git is the official source mirror of Git, a repository where the implementation of the version control system and the patch submission procedure can be checked.

GitHub description: Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.

stars
★ 64K
Forks
28.6K
Language
C
License
NOASSERTION
Read original source ↗View on GitHub ↗

git/git is the official source mirror of the distributed version control system Git. It is the core repository that implements version control features such as commits, branches, and merges, and its main language is C. This repository is operated for publishing only. If an improvement is submitted as a pull request, GitGitGadget can convert it into a patch for the mailing list, and the submission instructions point to the Documentation/SubmittingPatches procedure.

Git is a fast and scalable distributed version control system. Its rich set of commands gives access not only to everyday work but also to internal functionality. The README guides readers to installation instructions and a tutorial, frequently used commands, and per-command documentation. git/git is therefore used to look at both how to use Git and the source in which those features are implemented. The README also describes distribution under the GNU General Public License version 2 and GPLv2-compatible licensing for some parts.

However, the provided records contain neither the latest release nor the changes of that version. This material alone therefore does not allow you to judge what changed in a particular version. The license field is likewise recorded as the automatic determination NOASSERTION, so it must be read separately from the description in the README. These records suit understanding the character of the project and its submission path, but they are insufficient for tracking changes per release.