-The git configuration file contains a number of variables that affect
-the git command's behavior. The `.git/config` file in each repository
+The Git configuration file contains a number of variables that affect
+the Git commands' behavior. The `.git/config` file in each repository
is used to store the configuration for that repository, and
`$HOME/.gitconfig` is used to store a per-user configuration as
fallback values for the `.git/config` file. The file `/etc/gitconfig`
can be used to store a system-wide default configuration.
-The configuration variables are used by both the
+The configuration variables are used by both the it plumbing
and the porcelains. The variables are divided into sections, wherein
the fully qualified variable name of the variable itself is the last
dot-separated segment and the section name is everything before the last
If true, this option enables various workarounds to enable
git to work better on filesystems that are not case sensitive,
+it to work better on filesystems that are not case sensitive,
like FAT. For example, if a directory listing finds
- "makefile" when
git expects "Makefile", git will assume
+ "makefile" when it expects "Makefile", it will assume
it is really the same file, and continue to remember it as
- This option is only used by Mac OS implementation of git.
- When core.precomposeunicode=true, git reverts the unicode decomposition
+ This option is only used by Mac OS implementation of Git.
+ When core.precomposeunicode=true, Git reverts the unicode decomposition
of filenames done by Mac OS. This is useful when sharing a repository
between Mac OS and Linux or Windows.
- (Git for Windows 1.7.10 or higher is needed, or git under cygwin 1.7).
- When false, file names are handled fully transparent by git,
- which is backward compatible with older versions of git.
+ (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).
+ When false, file names are handled fully transparent by Git,
+ which is backward compatible with older versions of Git.
If false, the ctime differences between the index and the
- If true, makes
git check if converting `CRLF` is reversible when
+ If true, makes it check if converting `CRLF` is reversible when
end-of-line conversion is active. Git will verify if a command
modifies a file in the work tree either directly or indirectly.
For example, committing a file followed by checking out the
same file should yield the original file in the work tree. If
this is not the case for the current setting of
- `core.autocrlf`, git will reject the file. The variable can
- be set to "warn", in which case git will only warn about an
+ `core.autocrlf`, Git will reject the file. The variable can
+ be set to "warn", in which case Git will only warn about an
irreversible conversion but continue the operation.
CRLF conversion bears a slight chance of corrupting data.
-When it is enabled,
git will convert CRLF to LF during commit and LF to
+When it is enabled, it will convert CRLF to LF during commit and LF to
CRLF during checkout. A file that contains a mixture of LF and
-CRLF before the commit cannot be recreated by
git. For text
+CRLF before the commit cannot be recreated by it. For text
files this is the right thing to do: it corrects line endings
such that we have only LF line endings in the repository.
But for binary files that are accidentally classified as text the
setting the conversion type explicitly in .gitattributes. Right
after committing you still have the original file in your work
tree and this file is not yet corrupted. You can explicitly tell
git that this file is binary and git will handle the file
+it that this file is binary and it will handle the file
Unfortunately, the desired effect of cleaning up text files with
A "proxy command" to execute (as 'command host port') instead
of establishing direct connection to the remote server when
- using the
git protocol for fetching. If the variable value is
+ using the it protocol for fetching. If the variable value is
in the "COMMAND for DOMAIN" format, the command is applied only
on hostnames ending with the specified domain string. This variable
may be set multiple times and is matched in the given order;
file in a ".git" subdirectory of a directory and its value differs
from the latter directory (e.g. "/path/to/.git/config" has
core.worktree set to "/different/path"), which is most likely a
git commands in the "/path/to" directory will
+misconfiguration. Running it commands in the "/path/to" directory will
still use "/different/path" as the root of the work tree and can cause
confusion unless you know what you are doing (e.g. you are creating a
read-only snapshot of the same index to a location different from the
several users in a group (making sure all the files and objects are
group-writable). When 'all' (or 'world' or 'everybody'), the
repository will be readable by all users, additionally to being
- group-shareable. When 'umask' (or 'false'),
git will use permissions
+ group-shareable. When 'umask' (or 'false'), it will use permissions
reported by umask(2). When '0xxx', where '0xxx' is an octal number,
files in the repository will have this mode value. '0xxx' will override
user's umask value (whereas the other options will only override
See linkgit:git-init. False by default.
- If true,
git will warn you if the ref name you passed it is ambiguous
+ If true, it will warn you if the ref name you passed it is ambiguous
and might match multiple refs in the .git/refs/ tree. True by default.
In addition to '.gitignore' (per-directory) and
git looks into this file for patterns
+ '.git/info/exclude', it looks into this file for patterns
of files which are not meant to be tracked. "`~/`" is expanded
to the value of `$HOME` and "`~user/`" to the specified user's
home directory. Its default value is $XDG_CONFIG_HOME/git/ignore.
In addition to '.gitattributes' (per-directory) and
git looks into this file for attributes
+ '.git/info/attributes', it looks into this file for attributes
(see linkgit:gitattributes). Path expansions are made the same
way as for `core.excludesfile`. Its default value is
$XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not
When not configured the default commit message editor is used instead.
- The command that
git will use to paginate output. Can
+ The command that it will use to paginate output. Can
be overridden with the `GIT_PAGER` environment
- variable. Note that
git sets the `LESS` environment
+ variable. Note that it sets the `LESS` environment
variable to `FRSX` if it is unset when it runs the
pager. One can change these settings by setting the
`LESS` variable to some other value. Alternately,
global basis by setting the `core.pager` option.
Setting `core.pager` has no effect on the `LESS`
environment variable behaviour above, so if you want
- to override
git's default settings this way, you need
+ to override it's default settings this way, you need
to be explicit. For example, to disable the S option
in a backward compatible manner, set `core.pager`
to `less -+S`. This will be passed to the shell by
git, which will translate the final command to
+it, which will translate the final command to
does not trigger if the character before such a carriage-return
is not a whitespace (not enabled by default).
* `tabwidth=<n>` tells how many character positions a tab occupies; this
- is relevant for `indent-with-non-tab` and when
git fixes `tab-in-indent`
+ is relevant for `indent-with-non-tab` and when it fixes `tab-in-indent`
errors. The default tab width is 8. Allowed values are 1 to 63.
This can speed up operations like 'git diff' and 'git status' especially
on filesystems like NFS that have weak caching semantics and thus
-relatively high IO latencies. With this set to 'true',
git will do the
+relatively high IO latencies. With this set to 'true', it will do the
index comparison to the filesystem data in parallel, allowing
Tells 'git add' to continue adding files when some files cannot be
added due to indexing errors. Equivalent to the '--ignore-errors'
- option of linkgit:git-add. Older versions of
git accept only
+ option of linkgit:git-add. Older versions of it accept only
`add.ignore-errors`, which does not follow the usual naming
- convention for configuration variables. Newer versions of
+ convention for configuration variables. Newer versions of it
honor `add.ignoreErrors` as well.
after defining "alias.last = cat-file commit HEAD", the invocation
"git last" is equivalent to "git cat-file commit HEAD". To avoid
confusion and troubles with script usage, aliases that
- hide existing
git commands are ignored. Arguments are split by
+ hide existing it commands are ignored. Arguments are split by
spaces, the usual shell quoting and escaping is supported.
quote pair and a backslash can be used to quote them.
When a new branch is created with 'git branch' or 'git checkout'
- that tracks another branch, this variable tells
git to set
+ that tracks another branch, this variable tells it to set
up pull to rebase instead of merge (see "branch.<name>.rebase").
When `never`, rebase is never automatically set to true.
When `local`, rebase is set to true for tracked branches of
one of `header` (the header text of the status message),
`added` or `updated` (files which are added but not committed),
`changed` (files which are changed but not added in the index),
- `untracked` (files which are not tracked by
+ `untracked` (files which are not tracked by it),
`branch` (the current branch), or
`nobranch` (the color the 'no branch' warning is shown in, defaulting
to red). The values of these variables may be specified as in
to `always` if you want all output not intended for machine
consumption to use color, to `true` or `auto` if you want such
output to use color when written to the terminal, or to `false` or
- `never` if you prefer
git commands not to use color unless enabled
+ `never` if you prefer it commands not to use color unless enabled
explicitly with some other configuration or the `--color` option.
- If the number of objects fetched over the
+ If the number of objects fetched over the it native
limit, then the objects will be unpacked into loose object
files. However if the number of received objects equals or
The default for format-patch is to output a signature containing
git version number. Use this variable to change that default.
+ the it version number. Use this variable to change that default.
Set this variable to the empty string ("") to suppress
If true, the server will look up the end-of-line conversion
attributes for files to determine the '-k' modes to use. If
- the attributes force
git to treat a file as text,
+ the attributes force it to treat a file as text,
the '-k' mode will be left blank so CVS clients will
treat it as text. If they suppress text conversion, the file
will be set with '-kb' mode, which suppresses any newline munging
Database used by git-cvsserver to cache revision information
- derived from the
git repository. The exact meaning depends on the
+ derived from the it repository. The exact meaning depends on the
used database driver, for SQLite (which is the default driver) this
is a filename. Supports variable substitution (see
linkgit:git-cvsserver for details). May not contain semicolons (`;`).
File containing previously stored cookie lines which should be used
- in the
git http session, if they match the server. The file format
+ in the it http session, if they match the server. The file format
of the file to read cookies from should be plain HTTP headers or
the Netscape/Mozilla cookie file format (see linkgit:curl).
NOTE that the file specified with http.cookiefile is only used as
git's password prompt for the SSL certificate. Otherwise
+ Enable it's password prompt for the SSL certificate. Otherwise
OpenSSL will prompt the user, possibly many times, if the
certificate or private key is encrypted. Can be overridden by the
'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
The HTTP USER_AGENT string presented to an HTTP server. The default
- value represents the version of the client
git such as git/1.7.1.
+ value represents the version of the client it such as git/1.7.1.
This option allows you to override this value to a more common value
such as Mozilla/4.0. This may be necessary, for instance, if
connecting through a firewall that restricts HTTP connections to a set
Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
- Character encoding the commit messages are stored in;
+ Character encoding the commit messages are stored in; it itself
does not care per se, but this information is necessary e.g. when
importing commits from emails or in the gitk graphical history
browser (and possibly at other places in the future or in other
`true` (i.e. keep the backup files).
- When invoking a custom merge tool,
git uses a set of temporary
+ When invoking a custom merge tool, it uses a set of temporary
files to pass to the tool. If the tool returns an error and this
variable is set to `true`, then these temporary files will be
preserved, otherwise they will be removed after the tool has
When rewriting commits with <command> (currently `amend` or
- `rebase`) and this variable is set to `true`,
+ `rebase`) and this variable is set to `true`, it
automatically copies your notes from the original to the
rewritten commit. Defaults to `true`, but see
warning. This is meant to reduce packing time on multiprocessor
machines. The required amount of memory for the delta search window
is however multiplied by the number of threads.
- Specifying 0 will cause
git to auto-detect the number of CPU's
+ Specifying 0 will cause it to auto-detect the number of CPU's
and set the number of threads accordingly.
and this config option ignored whenever the corresponding pack is
-If you have an old
git that does not understand the version 2 `*.idx` file,
+If you have an old it that does not understand the version 2 `*.idx` file,
cloning or fetching over a non native protocol (e.g. "http" and "rsync")
that will copy both `*.pack` file and corresponding `*.idx` file from the
other side may give you a repository that cannot be accessed with your
-older version of
git. If the `*.pack` file is smaller than 2 GB, however,
+older version of it. If the `*.pack` file is smaller than 2 GB, however,
you can use linkgit:git-index-pack on the *.pack file to regenerate
If the value is boolean, turns on or off pagination of the
- output of a particular
git subcommand when writing to a tty.
+ output of a particular it subcommand when writing to a tty.
Otherwise, turns on pagination for the subcommand using the
pager specified by the value of `pager.<cmd>`. If `--paginate`
or `--no-pager` is specified on the command line, it takes
The default merge strategy to use when pulling a single branch.
- Defines the action git push should take if no refspec is given
+ Defines the action git push should take if no refspec is given
on the command line, no refspec is configured in the remote, and
no refspec is implied by any of the options given on the command
line. Possible values are:
- Setting this to a value <vcs> will cause
git to interact with
+ Setting this to a value <vcs> will cause it to interact with
the remote with the git-remote-<vcs> helper.
By default, linkgit:git-repack creates packs that use
delta-base offset. If you need to share your repository with
git older than version 1.4.4, either directly or via a dumb
+it older than version 1.4.4, either directly or via a dumb
protocol such as http, then you need to set this option to
- "false" and repack. Access from old
git versions over the
+ "false" and repack. Access from old it versions over the
native protocol are unaffected by this option.
By default, linkgit:git-status shows paths relative to the
current directory. Setting this variable to `false` shows paths
- relative to the repository root (this was the default for
+ relative to the repository root (this was the default for it
large number of repositories, and serves them with multiple
access methods, and some users need to use different access
methods, this feature allows people to specify any of the
- equivalent URLs and have
git automatically rewrite the URL to
+ equivalent URLs and have it automatically rewrite the URL to
the best alternative for the particular user, even for a
never-before-seen repository on the site. When more than one
insteadOf strings match a given URL, the longest match is used.
resulting URL will be pushed to. In cases where some site serves
a large number of repositories, and serves them with multiple
access methods, some of which do not allow push, this feature
- allows people to specify a pull-only URL and have
+ allows people to specify a pull-only URL and have it
automatically use an appropriate URL to push, even for a
never-before-seen repository on the site. When more than one
pushInsteadOf strings match a given URL, the longest match is
- used. If a remote has an explicit pushurl,
git will ignore this
+ used. If a remote has an explicit pushurl, it will ignore this