Table of Contents


Visión de conjunto

The stupid content tracker


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.

See gittutorial(7) to get started, then see giteveryday(7) for a useful minimum set of commands. The Git User's Manual has a more in-depth introduction.

After you mastered the basic concepts, you can come back to this page to learn what commands Git offers. You can learn more about individual Git commands with "git help command". gitcli(7) manual page gives you an overview of the command-line command syntax.

A formatted and hyperlinked copy of the latest Git documentation can be viewed at


Actualmente la última versión es 2.16.2.

Versión Fecha de lanzamiento original Última versión Fecha de lanzamiento
0.99 2005-07-11 0.99.9n 2005-12-15
1.0 2005-12-21 1.0.13 2006-01-27
1.1 2006-01-08 1.1.6 2006-01-30
1.2 2006-02-12 1.2.6 2006-04-08
1.3 2006-04-18 1.3.3 2006-05-16
1.4 2006-06-10 2008-07-16
1.5 2007-02-14 2008-12-17
1.6 2008-08-17 2010-12-15
1.7 2010-02-13 2012-10-17
1.8 2012-10-21 2014-12-17
1.9 2014-02-14 1.9.5 2014-12-17
2.0 2014-05-28 2.0.5 2014-12-17
2.1 2014-08-16 2.1.4 2014-12-17
2.2 2014-11-26 2.2.3 2015-09-04
2.3 2015-02-05 2.3.10 2015-09-29
2.4 2015-04-30 2.4.12 2017-05-05
2.5 2015-07-27 2.5.6 2017-05-05
2.6 2015-09-28 2.6.7 2017-05-05
2.7 2015-10-04 2.7.5 2017-05-05
2.8 2016-03-28 2.8.5 2017-05-05
2.9 2016-06-13 2.9.4 2017-05-05
2.10 2016-09-02 2.10.3 2017-05-05
2.11 2016-11-29 2.11.2 2017-05-05
2.12 2017-02-24 2.12.3 2017-05-05
2.13 2017-05-10 2.13.4 2017-08-01
2.14 2017-08-04 2.14.3 2017-10-24
2.15 2017-10-30 2.15.1 2017-11-28
2.16 2018-01-17 2.16.2 2018-02-15

Cómo instalar

Requisitos previos



$ sudo apt-add-repository ppa:git-core/ppa
$ sudo apt-get update
$ sudo apt-get install git


$ sudo yum install git


$ sudo yum install git-core

Arch Linux

$ sudo pacman -Sy git


$ sudo emerge --ask --verbose dev-vcs/git


$ brew install git

Paquetes instalados


$ git --version
git version 2.16.2



git [--version] [--help] [-C <path>] [-c <name>=<value>]
    [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
    [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
    [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
    <command> [<args>]


Esto se actualiza para la versión 2.16.2.

  • --version : Prints the Git suite version that the git program came from.
  • --help : Prints the synopsis and a list of the most commonly used commands. If the option --all or -a is given then all available commands are printed. If a Git command is named this option will bring up the manual page for that command. Other options are available to control how the manual page is displayed. See git-help for more information, because git --help ... is converted internally into git help ....
  • -C : Run as if git was started in <path> instead of the current working directory. When multiple -C options are given, each subsequent non-absolute -C <path> is interpreted relative to the preceding -C <path>. This option affects options that expect path name like --git-dir and --work-tree in that their interpretations of the path names would be made relative to the working directory caused by the -C option. For example the following invocations are equivalent:

    git --git-dir=a.git --work-tree=b -C c status

    git --git-dir=c/a.git --work-tree=c/b status

  • -c = : Pass a configuration parameter to the command. The value given will override values from configuration files. The <name> is expected in the same format as listed by git config (subkeys separated by dots).

    Note that omitting the = in git -c ... is allowed and sets to the boolean true value (just like [foo]bar would in a config file). Including the equals but with an empty value (like git -c ...) sets to the empty string which git config --bool will convert to false.

  • --exec-path[=] : Path to wherever your core Git programs are installed. This can also be controlled by setting the GIT_EXEC_PATH environment variable. If no path is given, git will print the current setting and then exit.
  • --html-path : Print the path, without trailing slash, where Git’s HTML documentation is installed and exit.
  • --man-path : Print the manpath (see man(1)) for the man pages for this version of Git and exit.
  • --info-path : Print the path where the Info files documenting this version of Git are installed and exit.
  • -p, --paginate : Pipe all output into less (or if set, $PAGER) if standard output is a terminal. This overrides the pager.<cmd> configuration options (see the "Configuration Mechanism" section below).
  • --no-pager : Do not pipe Git output into a pager.
  • --git-dir= : Set the path to the repository. This can also be controlled by setting the GIT_DIR environment variable. It can be an absolute path or relative path to current working directory.
  • --work-tree= : Set the path to the working tree. It can be an absolute path or a path relative to the current working directory. This can also be controlled by setting the GIT_WORK_TREE environment variable and the core.worktree configuration variable (see core.worktree in git-config for a more detailed discussion).
  • --namespace= : Set the Git namespace. See gitnamespaces for more details. Equivalent to setting the GIT_NAMESPACE environment variable.
  • --super-prefix= : Currently for internal use only. Set a prefix which gives a path from above a repository down to its root. One use is to give submodules context about the superproject that invoked it.
  • --bare : Treat the repository as a bare repository. If GIT_DIR environment is not set, it is set to the current working directory.
  • --no-replace-objects : Do not use replacement refs to replace Git objects. See git-replace for more information.
  • --literal-pathspecs : Treat pathspecs literally (i.e. no globbing, no pathspec magic). This is equivalent to setting the GIT_LITERAL_PATHSPECS environment variable to 1.
  • --glob-pathspecs : Add "glob" magic to all pathspec. This is equivalent to setting the GIT_GLOB_PATHSPECS environment variable to 1. Disabling globbing on individual pathspecs can be done using pathspec magic ":(literal)"
  • --noglob-pathspecs : Add "literal" magic to all pathspec. This is equivalent to setting the GIT_NOGLOB_PATHSPECS environment variable to 1. Enabling globbing on individual pathspecs can be done using pathspec magic ":(glob)"
  • --icase-pathspecs : Add "icase" magic to all pathspec. This is equivalent to setting the GIT_ICASE_PATHSPECS environment variable to 1.
  • --no-optional-locks : Do not perform optional operations that require locks. This is equivalent to setting the GIT_OPTIONAL_LOCKS to 0.



Clone a repository into a new directory


Create an empty Git repository or reinitialize an existing one


Add file contents to the index


Move or rename a file, a directory, or a symlink


Reset current HEAD to the specified state


Remove files from the working tree and from the index


Use binary search to find the commit that introduced a bug


Print lines matching a pattern


Show commit logs


Show various types of objects


Show the working tree status


List, create, or delete branches


Switch branches or restore working tree files


Record changes to the repository


Show changes between commits, commit and working tree, etc


Join two or more development histories together


Reapply commits on top of another base tip


Create, list, delete or verify a tag object signed with GPG


Download objects and refs from another repository


Fetch from and integrate with another repository or a local branch


Update remote refs along with associated objects


Date: 2018-02-24

Author: Dongsoo Lee

Created: 2018-12-10 Mon 03:09