Skip to content
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.

feat: Reformat list of names in "Naming" section as markdown list #2 #54

Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions git-text-content.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ The development of Git began on 3 April 2005.[17] Torvalds announced the project
Torvalds turned over maintenance on 26 July 2005 to Junio Hamano, a major contributor to the project.[22] Hamano was responsible for the 1.0 release on 21 December 2005.[23]

## Naming

Torvalds sarcastically quipped about the name git (which means "unpleasant person" in British English slang): "I'm an egotistical bastard, and I name all my projects after myself. First 'Linux', now 'git'."[24][25] The man page describes Git as "the stupid content tracker".[26] The read-me file of the source code elaborates further:[27]

"git" can mean anything, depending on your mood.
Expand All @@ -34,6 +35,12 @@ The source code for Git refers to the program as, "the information manager from
Design
Git's design was inspired by BitKeeper and Monotone.[38][39] Git was originally designed as a low-level version-control system engine, on top of which others could write front ends, such as Cogito or StGIT.[39] The core Git project has since become a complete version-control system that is usable directly.[40] While strongly influenced by BitKeeper, Torvalds deliberately avoided conventional approaches, leading to a unique design.[41]

### List of Git Names (Not sure where original list is...)
1. "Upleasant Person"
1. "Global Information Tracker"
1. "Goddamn Idiotic Truckload of Sh*t"
1. "Useless Person/Entity"

## Characteristics

Git's design is a synthesis of Torvalds's experience with Linux in maintaining a large distributed development project, along with his intimate knowledge of file-system performance gained from the same project and the urgent need to produce a working system in short order. These influences led to the following implementation choices:[42]
Expand Down