The Architecture of Git

6.1. Git in a Nutshell

Git enables the maintenance of a digital body of work (often, but not limited
to, code) by many collaborators using a peer-to-peer network of
repositories. It supports distributed workflows, allowing a
body of work to either eventually converge or temporarily diverge.

This chapter will show how various aspects of Git work under the covers
to enable this, and how it differs from other version control systems (VCSs).

6.2. Git’s Origin

To understand Git’s design philosophy better it is helpful to understand the
circumstances in which the Git project was started in the Linux Kernel
Community.

The Linux kernel was unusual, compared to most commercial software projects at that
time, because of the large number of committers and the high variance of
contributor involvement and knowledge of the existing
codebase.
The kernel had been maintained via tarballs and patches for years, and
the core development community struggled to find a VCS that
satisfied most of their needs.

Git is an open


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/b970EvA5uXo/git.html

Original article

Comments are closed.

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: