pub/scm/git/git.git  about / heads / tags
The core git plumbing
$ git log --pretty=format:'%h %s (%cs)%d'
fe86abd751 Git 2.41 (2023-06-01)
	(HEAD -> master, tag: v2.41.0, main)
ee65a63819 Merge tag 'l10n-2.41.0-2' of (2023-06-01)
f86de088f8 l10n: zh_TW.po: Git 2.41.0 (2023-06-01)
81a797fcdf Merge branch 'add-uk-initial-l10n' of (2023-05-31)
308f3f4e9a l10n: sv.po: Update Swedish translation (5515t0f0u) (2023-05-31)
aa1991d080 l10n: Update Catalan translation (2023-05-26)
97e736c4cc Merge branch 'l10n-de-2.41' of (2023-05-25)
2f88193dac Merge branch 'catalan' of (2023-05-25)
4d34454e2c Merge branch 'tr' of (2023-05-25)
08af8c4c48 Merge branch 'main' of (2023-05-25)

$ git cat-file blob
[![Build status](](

Git - fast, scalable, distributed revision control system

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-<commandname>.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-<commandname>` 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

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to (read
[Documentation/SubmittingPatches][] for instructions on patch submission
and [Documentation/CodingGuidelines][]).

Those wishing to help with error message, usage and informational message
string translations (localization l10) should see [po/][]
(a `po` file is a Portable Object file that holds the translations).

To subscribe to the list, send an email with just "subscribe git" in
the body to (not the Git list). The mailing
list archives are available at <>,
<> and other archival sites.

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.

The name "git" was given by Linus Torvalds when he wrote the very
first version. He described the tool as "the stupid content tracker"
and the name as (depending on your mood):

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

[Documentation/gittutorial.txt]: Documentation/gittutorial.txt
[Documentation/giteveryday.txt]: Documentation/giteveryday.txt
[Documentation/gitcvs-migration.txt]: Documentation/gitcvs-migration.txt
[Documentation/SubmittingPatches]: Documentation/SubmittingPatches
[Documentation/CodingGuidelines]: Documentation/CodingGuidelines
[po/]: po/

# heads (aka `branches'):
$ git for-each-ref --sort=-creatordate refs/heads \
	--format='%(HEAD) %(refname:short) %(subject) (%(creatordate:short))'
  todo         What's cooking (2023/06 #01) (2023-06-01)
  next         Sync with Git 2.41 (2023-06-01)
  seen         Merge branch 'cc/git-replay' into seen (2023-06-01)
  main         Git 2.41 (2023-06-01)
* master       Git 2.41 (2023-06-01)
  maint        Git 2.40.1 (2023-04-17)

# tags:
$ git for-each-ref --sort=-creatordate refs/tags \
	--format='%(refname:short) %(subject) (%(creatordate:short))'
v2.41.0      Git 2.41 (2023-06-01)	tar.gz
v2.41.0-rc2  Git 2.41-rc2 (2023-05-25)	tar.gz
v2.41.0-rc1  Git 2.41-rc1 (2023-05-19)	tar.gz
v2.41.0-rc0  Git 2.41-rc0 (2023-05-15)	tar.gz
v2.39.3      Git 2.39.3 (2023-04-17)	tar.gz
v2.40.1      Git 2.40.1 (2023-04-17)	tar.gz
v2.35.8      Git 2.35.8 (2023-04-17)	tar.gz
v2.36.6      Git 2.36.6 (2023-04-17)	tar.gz
v2.37.7      Git 2.37.7 (2023-04-17)	tar.gz
v2.38.5      Git 2.38.5 (2023-04-17)	tar.gz

git clone