Google Git
Sign in
chromium / external / gitster / git-htmldocs / ee62a7b284d15bc30fbbca7fd3bf86710de148bc / . / git-config.html
blob: 74bccbfc69b86b405bf33f3bf9c0c83677f02dae [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="generator" content="AsciiDoc 7.0.2" />
<style type="text/css">
/* Debug borders */
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
/*
border: 1px solid red;
*/
}
body {
margin: 1em 5% 1em 5%;
}
a { color: blue; }
a:visited { color: fuchsia; }
em {
font-style: italic;
}
strong {
font-weight: bold;
}
tt {
color: navy;
}
h1, h2, h3, h4, h5, h6 {
color: #527bbd;
font-family: sans-serif;
margin-top: 1.2em;
margin-bottom: 0.5em;
line-height: 1.3;
}
h1 {
border-bottom: 2px solid silver;
}
h2 {
border-bottom: 2px solid silver;
padding-top: 0.5em;
}
div.sectionbody {
font-family: serif;
margin-left: 0;
}
hr {
border: 1px solid silver;
}
p {
margin-top: 0.5em;
margin-bottom: 0.5em;
}
pre {
padding: 0;
margin: 0;
}
span#author {
color: #527bbd;
font-family: sans-serif;
font-weight: bold;
font-size: 1.2em;
}
span#email {
}
span#revision {
font-family: sans-serif;
}
div#footer {
font-family: sans-serif;
font-size: small;
border-top: 2px solid silver;
padding-top: 0.5em;
margin-top: 4.0em;
}
div#footer-text {
float: left;
padding-bottom: 0.5em;
}
div#footer-badges {
float: right;
padding-bottom: 0.5em;
}
div#preamble,
div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
div.admonitionblock {
margin-right: 10%;
margin-top: 1.5em;
margin-bottom: 1.5em;
}
div.admonitionblock {
margin-top: 2.5em;
margin-bottom: 2.5em;
}
div.content { /* Block element content. */
padding: 0;
}
/* Block element titles. */
div.title, caption.title {
font-family: sans-serif;
font-weight: bold;
text-align: left;
margin-top: 1.0em;
margin-bottom: 0.5em;
}
div.title + * {
margin-top: 0;
}
td div.title:first-child {
margin-top: 0.0em;
}
div.content div.title:first-child {
margin-top: 0.0em;
}
div.content + div.title {
margin-top: 0.0em;
}
div.sidebarblock > div.content {
background: #ffffee;
border: 1px solid silver;
padding: 0.5em;
}
div.listingblock > div.content {
border: 1px solid silver;
background: #f4f4f4;
padding: 0.5em;
}
div.quoteblock > div.content {
padding-left: 2.0em;
}
div.quoteblock .attribution {
text-align: right;
}
div.admonitionblock .icon {
vertical-align: top;
font-size: 1.1em;
font-weight: bold;
text-decoration: underline;
color: #527bbd;
padding-right: 0.5em;
}
div.admonitionblock td.content {
padding-left: 0.5em;
border-left: 2px solid silver;
}
div.exampleblock > div.content {
border-left: 2px solid silver;
padding: 0.5em;
}
div.verseblock div.content {
white-space: pre;
}
div.imageblock div.content { padding-left: 0; }
div.imageblock img { border: 1px solid silver; }
span.image img { border-style: none; }
dl {
margin-top: 0.8em;
margin-bottom: 0.8em;
}
dt {
margin-top: 0.5em;
margin-bottom: 0;
font-style: italic;
}
dd > *:first-child {
margin-top: 0;
}
ul, ol {
list-style-position: outside;
}
ol.olist2 {
list-style-type: lower-alpha;
}
div.tableblock > table {
border-color: #527bbd;
border-width: 3px;
}
thead {
font-family: sans-serif;
font-weight: bold;
}
tfoot {
font-weight: bold;
}
div.hlist {
margin-top: 0.8em;
margin-bottom: 0.8em;
}
td.hlist1 {
vertical-align: top;
font-style: italic;
padding-right: 0.8em;
}
td.hlist2 {
vertical-align: top;
}
@media print {
div#footer-badges { display: none; }
}
include::./stylesheets/xhtml11-manpage.css[]
/* Workarounds for IE6's broken and incomplete CSS2. */
div.sidebar-content {
background: #ffffee;
border: 1px solid silver;
padding: 0.5em;
}
div.sidebar-title, div.image-title {
font-family: sans-serif;
font-weight: bold;
margin-top: 0.0em;
margin-bottom: 0.5em;
}
div.listingblock div.content {
border: 1px solid silver;
background: #f4f4f4;
padding: 0.5em;
}
div.quoteblock-content {
padding-left: 2.0em;
}
div.exampleblock-content {
border-left: 2px solid silver;
padding-left: 0.5em;
}
</style>
<title>git-config(1)</title>
</head>
<body>
<div id="header">
<h1>
git-config(1) Manual Page
</h1>
<h2>NAME</h2>
<div class="sectionbody">
<p>git-config -
Get and set repository or global options
</p>
</div>
</div>
<h2>SYNOPSIS</h2>
<div class="sectionbody">
<div class="verseblock">
<div class="content"><em>git-config</em> [--system | --global] [type] name [value [value_regex]]
<em>git-config</em> [--system | --global] [type] --add name value
<em>git-config</em> [--system | --global] [type] --replace-all name [value [value_regex]]
<em>git-config</em> [--system | --global] [type] --get name [value_regex]
<em>git-config</em> [--system | --global] [type] --get-all name [value_regex]
<em>git-config</em> [--system | --global] [type] --unset name [value_regex]
<em>git-config</em> [--system | --global] [type] --unset-all name [value_regex]
<em>git-config</em> [--system | --global] [type] --rename-section old_name new_name
<em>git-config</em> [--system | --global] [type] --remove-section name
<em>git-config</em> [--system | --global] -l | --list</div></div>
</div>
<h2>DESCRIPTION</h2>
<div class="sectionbody">
<p>You can query/set/replace/unset options with this command. The name is
actually the section and the key separated by a dot, and the value will be
escaped.</p>
<p>Multiple lines can be added to an option by using the <em>--add</em> option.
If you want to update or unset an option which can occur on multiple
lines, a POSIX regexp <tt>value_regex</tt> needs to be given. Only the
existing values that match the regexp are updated or unset. If
you want to handle the lines that do <strong>not</strong> match the regex, just
prepend a single exclamation mark in front (see EXAMPLES).</p>
<p>The type specifier can be either <em>--int</em> or <em>--bool</em>, which will make
<em>git-config</em> ensure that the variable(s) are of the given type and
convert the value to the canonical form (simple decimal number for int,
a "true" or "false" string for bool). If no type specifier is passed,
no checks or transformations are performed on the value.</p>
<p>This command will fail if:</p>
<ol>
<li>
<p>
The .git/config file is invalid,
</p>
</li>
<li>
<p>
Can not write to .git/config,
</p>
</li>
<li>
<p>
no section was provided,
</p>
</li>
<li>
<p>
the section or key is invalid,
</p>
</li>
<li>
<p>
you try to unset an option which does not exist,
</p>
</li>
<li>
<p>
you try to unset/set an option for which multiple lines match, or
</p>
</li>
<li>
<p>
you use --global option without $HOME being properly set.
</p>
</li>
</ol>
</div>
<h2>OPTIONS</h2>
<div class="sectionbody">
<dl>
<dt>
--replace-all
</dt>
<dd>
<p>
Default behavior is to replace at most one line. This replaces
all lines matching the key (and optionally the value_regex).
</p>
</dd>
<dt>
--add
</dt>
<dd>
<p>
Adds a new line to the option without altering any existing
values. This is the same as providing <em>^$</em> as the value_regex.
</p>
</dd>
<dt>
--get
</dt>
<dd>
<p>
Get the value for a given key (optionally filtered by a regex
matching the value). Returns error code 1 if the key was not
found and error code 2 if multiple key values were found.
</p>
</dd>
<dt>
--get-all
</dt>
<dd>
<p>
Like get, but does not fail if the number of values for the key
is not exactly one.
</p>
</dd>
<dt>
--get-regexp
</dt>
<dd>
<p>
Like --get-all, but interprets the name as a regular expression.
</p>
</dd>
<dt>
--global
</dt>
<dd>
<p>
Use global ~/.gitconfig file rather than the repository .git/config.
</p>
</dd>
<dt>
--system
</dt>
<dd>
<p>
Use system-wide $(prefix)/etc/gitconfig rather than the repository
.git/config.
</p>
</dd>
<dt>
--remove-section
</dt>
<dd>
<p>
Remove the given section from the configuration file.
</p>
</dd>
<dt>
--rename-section
</dt>
<dd>
<p>
Rename the given section to a new name.
</p>
</dd>
<dt>
--unset
</dt>
<dd>
<p>
Remove the line matching the key from config file.
</p>
</dd>
<dt>
--unset-all
</dt>
<dd>
<p>
Remove all lines matching the key from config file.
</p>
</dd>
<dt>
-l, --list
</dt>
<dd>
<p>
List all variables set in config file.
</p>
</dd>
<dt>
--bool
</dt>
<dd>
<p>
git-config will ensure that the output is "true" or "false"
</p>
</dd>
<dt>
--int
</dt>
<dd>
<p>
git-config will ensure that the output is a simple
decimal number. An optional value suffix of <em>k</em>, <em>m</em>, or <em>g</em>
in the config file will cause the value to be multiplied
by 1024, 1048576, or 1073741824 prior to output.
</p>
</dd>
</dl>
</div>
<h2>ENVIRONMENT</h2>
<div class="sectionbody">
<dl>
<dt>
GIT_CONFIG
</dt>
<dd>
<p>
Take the configuration from the given file instead of .git/config.
Using the "--global" option forces this to ~/.gitconfig.
</p>
</dd>
<dt>
GIT_CONFIG_LOCAL
</dt>
<dd>
<p>
Currently the same as $GIT_CONFIG; when Git will support global
configuration files, this will cause it to take the configuration
from the global configuration file in addition to the given file.
</p>
</dd>
</dl>
</div>
<h2>EXAMPLE</h2>
<div class="sectionbody">
<p>Given a .git/config like this:</p>
<div class="literalblock">
<div class="content">
<pre><tt>#
# This is the config file, and
# a '#' or ';' character indicates
# a comment
#</tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><tt>; core variables
[core]
; Don't trust file modes
filemode = false</tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><tt>; Our diff algorithm
[diff]
external = "/usr/local/bin/gnu-diff -u"
renames = true</tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><tt>; Proxy settings
[core]
gitproxy="ssh" for "ssh://kernel.org/"
gitproxy="proxy-command" for kernel.org
gitproxy="myprotocol-command" for "my://"
gitproxy=default-proxy ; for all the rest</tt></pre>
</div></div>
<p>you can set the filemode to true with</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config core.filemode true</tt></pre>
</div></div>
<p>The hypothetical proxy command entries actually have a postfix to discern
what URL they apply to. Here is how to change the entry for kernel.org
to "ssh".</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config core.gitproxy '"ssh" for kernel.org' 'for kernel.org$'</tt></pre>
</div></div>
<p>This makes sure that only the key/value pair for kernel.org is replaced.</p>
<p>To delete the entry for renames, do</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config --unset diff.renames</tt></pre>
</div></div>
<p>If you want to delete an entry for a multivar (like core.gitproxy above),
you have to provide a regex matching the value of exactly one line.</p>
<p>To query the value for a given key, do</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config --get core.filemode</tt></pre>
</div></div>
<p>or</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config core.filemode</tt></pre>
</div></div>
<p>or, to query a multivar:</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config --get core.gitproxy "for kernel.org$"</tt></pre>
</div></div>
<p>If you want to know all the values for a multivar, do:</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config --get-all core.gitproxy</tt></pre>
</div></div>
<p>If you like to live dangerous, you can replace <strong>all</strong> core.gitproxy by a
new one with</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config --replace-all core.gitproxy ssh</tt></pre>
</div></div>
<p>However, if you really only want to replace the line for the default proxy,
i.e. the one without a "for &#8230;" postfix, do something like this:</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config core.gitproxy ssh '! for '</tt></pre>
</div></div>
<p>To actually match only values with an exclamation mark, you have to</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config section.key value '[!]'</tt></pre>
</div></div>
<p>To add a new proxy, without altering any of the existing ones, use</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git config core.gitproxy '"proxy" for example.com'</tt></pre>
</div></div>
</div>
<h2>CONFIGURATION FILE</h2>
<div class="sectionbody">
<p>The git configuration file contains a number of variables that affect
the git command's behavior. <tt>.git/config</tt> file for each repository
is used to store the information for that repository, and
<tt>$HOME/.gitconfig</tt> is used to store per user information to give
fallback values for <tt>.git/config</tt> file. The file <tt>/etc/gitconfig</tt>
can be used to store system-wide defaults.</p>
<p>They can be used by both the git plumbing
and the porcelains. The variables are divided into sections, where
in the fully qualified variable name the variable itself is the last
dot-separated segment and the section name is everything before the last
dot. The variable names are case-insensitive and only alphanumeric
characters are allowed. Some variables may appear multiple times.</p>
<h3>Syntax</h3>
<p>The syntax is fairly flexible and permissive; whitespaces are mostly
ignored. The <em>#</em> and <em>;</em> characters begin comments to the end of line,
blank lines are ignored.</p>
<p>The file consists of sections and variables. A section begins with
the name of the section in square brackets and continues until the next
section begins. Section names are not case sensitive. Only alphanumeric
characters, <em><tt>-</tt></em> and <em><tt>.</tt></em> are allowed in section names. Each variable
must belong to some section, which means that there must be section
header before first setting of a variable.</p>
<p>Sections can be further divided into subsections. To begin a subsection
put its name in double quotes, separated by space from the section name,
in the section header, like in example below:</p>
<div class="listingblock">
<div class="content">
<pre><tt> [section "subsection"]
</tt></pre>
</div></div>
<p>Subsection names can contain any characters except newline (doublequote
<em><tt>"</tt></em> and backslash have to be escaped as <em><tt>\"</tt></em> and <em><tt>\\</tt></em>,
respectively) and are case sensitive. Section header cannot span multiple
lines. Variables may belong directly to a section or to a given subsection.
You can have <tt>[section]</tt> if you have <tt>[section "subsection"]</tt>, but you
don't need to.</p>
<p>There is also (case insensitive) alternative <tt>[section.subsection]</tt> syntax.
In this syntax subsection names follow the same restrictions as for section
name.</p>
<p>All the other lines are recognized as setting variables, in the form
<em>name = value</em>. If there is no equal sign on the line, the entire line
is taken as <em>name</em> and the variable is recognized as boolean "true".
The variable names are case-insensitive and only alphanumeric
characters and <em><tt>-</tt></em> are allowed. There can be more than one value
for a given variable; we say then that variable is multivalued.</p>
<p>Leading and trailing whitespace in a variable value is discarded.
Internal whitespace within a variable value is retained verbatim.</p>
<p>The values following the equals sign in variable assign are all either
a string, an integer, or a boolean. Boolean values may be given as yes/no,
0/1 or true/false. Case is not significant in boolean values, when
converting value to the canonical form using <em>--bool</em> type specifier;
<tt>git-config</tt> will ensure that the output is "true" or "false".</p>
<p>String values may be entirely or partially enclosed in double quotes.
You need to enclose variable value in double quotes if you want to
preserve leading or trailing whitespace, or if variable value contains
beginning of comment characters (if it contains <em>#</em> or <em>;</em>).
Double quote <em><tt>"</tt></em> and backslash <em><tt>\</tt></em> characters in variable value must
be escaped: use <em><tt>\"</tt></em> for <em><tt>"</tt></em> and <em><tt>\\</tt></em> for <em><tt>\</tt></em>.</p>
<p>The following escape sequences (beside <em><tt>\"</tt></em> and <em><tt>\\</tt></em>) are recognized:
<em><tt>\n</tt></em> for newline character (NL), <em><tt>\t</tt></em> for horizontal tabulation (HT, TAB)
and <em><tt>\b</tt></em> for backspace (BS). No other char escape sequence, nor octal
char sequences are valid.</p>
<p>Variable value ending in a <em><tt>\</tt></em> is continued on the next line in the
customary UNIX fashion.</p>
<p>Some variables may require special value format.</p>
<h3>Example</h3>
<div class="literalblock">
<div class="content">
<pre><tt># Core variables
[core]
; Don't trust file modes
filemode = false</tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><tt># Our diff algorithm
[diff]
external = "/usr/local/bin/gnu-diff -u"
renames = true</tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><tt>[branch "devel"]
remote = origin
merge = refs/heads/devel</tt></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><tt># Proxy settings
[core]
gitProxy="ssh" for "ssh://kernel.org/"
gitProxy=default-proxy ; for the rest</tt></pre>
</div></div>
<h3>Variables</h3>
<p>Note that this list is non-comprehensive and not necessarily complete.
For command-specific variables, you will find a more detailed description
in the appropriate manual page. You will find a description of non-core
porcelain configuration variables in the respective porcelain documentation.</p>
<dl>
<dt>
core.fileMode
</dt>
<dd>
<p>
If false, the executable bit differences between the index and
the working copy are ignored; useful on broken filesystems like FAT.
See <a href="git-update-index.html">git-update-index(1)</a>. True by default.
</p>
</dd>
<dt>
core.autocrlf
</dt>
<dd>
<p>
If true, makes git convert <tt>CRLF</tt> at the end of lines in text files to
<tt>LF</tt> when reading from the filesystem, and convert in reverse when
writing to the filesystem. The variable can be set to
<em>input</em>, in which case the conversion happens only while
reading from the filesystem but files are written out with
<tt>LF</tt> at the end of lines. Currently, which paths to consider
"text" (i.e. be subjected to the autocrlf mechanism) is
decided purely based on the contents.
</p>
</dd>
<dt>
core.symlinks
</dt>
<dd>
<p>
If false, symbolic links are checked out as small plain files that
contain the link text. <a href="git-update-index.html">git-update-index(1)</a> and
<a href="git-add.html">git-add(1)</a> will not change the recorded type to regular
file. Useful on filesystems like FAT that do not support
symbolic links. True by default.
</p>
</dd>
<dt>
core.gitProxy
</dt>
<dd>
<p>
A "proxy command" to execute (as <em>command host port</em>) instead
of establishing direct connection to the remote server when
using the git 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;
the first match wins.
</p>
<p>Can be overridden by the <em>GIT_PROXY_COMMAND</em> environment variable
(which always applies universally, without the special "for"
handling).</p>
</dd>
<dt>
core.ignoreStat
</dt>
<dd>
<p>
The working copy files are assumed to stay unchanged until you
mark them otherwise manually - Git will not detect the file changes
by lstat() calls. This is useful on systems where those are very
slow, such as Microsoft Windows. See <a href="git-update-index.html">git-update-index(1)</a>.
False by default.
</p>
</dd>
<dt>
core.preferSymlinkRefs
</dt>
<dd>
<p>
Instead of the default "symref" format for HEAD
and other symbolic reference files, use symbolic links.
This is sometimes needed to work with old scripts that
expect HEAD to be a symbolic link.
</p>
</dd>
<dt>
core.bare
</dt>
<dd>
<p>
If true this repository is assumed to be <em>bare</em> and has no
working directory associated with it. If this is the case a
number of commands that require a working directory will be
disabled, such as <a href="git-add.html">git-add(1)</a> or <a href="git-merge.html">git-merge(1)</a>.
</p>
<p>This setting is automatically guessed by <a href="git-clone.html">git-clone(1)</a> or
<a href="git-init.html">git-init(1)</a> when the repository was created. By default a
repository that ends in "/.git" is assumed to be not bare (bare =
false), while all other repositories are assumed to be bare (bare
= true).</p>
</dd>
<dt>
core.logAllRefUpdates
</dt>
<dd>
<p>
Updates to a ref &lt;ref&gt; is logged to the file
"$GIT_DIR/logs/&lt;ref&gt;", by appending the new and old
SHA1, the date/time and the reason of the update, but
only when the file exists. If this configuration
variable is set to true, missing "$GIT_DIR/logs/&lt;ref&gt;"
file is automatically created for branch heads.
</p>
<p>This information can be used to determine what commit
was the tip of a branch "2 days ago".</p>
<p>This value is true by default in a repository that has
a working directory associated with it, and false by
default in a bare repository.</p>
</dd>
<dt>
core.repositoryFormatVersion
</dt>
<dd>
<p>
Internal variable identifying the repository format and layout
version.
</p>
</dd>
<dt>
core.sharedRepository
</dt>
<dd>
<p>
When <em>group</em> (or <em>true</em>), the repository is made shareable between
several users in a group (making sure all the files and objects are
group-writable). When <em>all</em> (or <em>world</em> or <em>everybody</em>), the
repository will be readable by all users, additionally to being
group-shareable. When <em>umask</em> (or <em>false</em>), git will use permissions
reported by umask(2). See <a href="git-init.html">git-init(1)</a>. False by default.
</p>
</dd>
<dt>
core.warnAmbiguousRefs
</dt>
<dd>
<p>
If true, git 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.
</p>
</dd>
<dt>
core.compression
</dt>
<dd>
<p>
An integer -1..9, indicating the compression level for objects that
are not in a pack file. -1 is the zlib and git default. 0 means no
compression, and 1..9 are various speed/size tradeoffs, 9 being
slowest.
</p>
</dd>
<dt>
core.legacyheaders
</dt>
<dd>
<p>
A boolean which
changes the format of loose objects so that they are more
efficient to pack and to send out of the repository over git
native protocol, since v1.4.2. However, loose objects
written in the new format cannot be read by git older than
that version; people fetching from your repository using
older versions of git over dumb transports (e.g. http)
will also be affected.
</p>
<p>To let git use the new loose object format, you have to
set core.legacyheaders to false.</p>
</dd>
<dt>
core.packedGitWindowSize
</dt>
<dd>
<p>
Number of bytes of a pack file to map into memory in a
single mapping operation. Larger window sizes may allow
your system to process a smaller number of large pack files
more quickly. Smaller window sizes will negatively affect
performance due to increased calls to the operating system's
memory manager, but may improve performance when accessing
a large number of large pack files.
</p>
<p>Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should
be reasonable for all users/operating systems. You probably do
not need to adjust this value.</p>
<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
</dd>
<dt>
core.packedGitLimit
</dt>
<dd>
<p>
Maximum number of bytes to map simultaneously into memory
from pack files. If Git needs to access more than this many
bytes at once to complete an operation it will unmap existing
regions to reclaim virtual address space within the process.
</p>
<p>Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
This should be reasonable for all users/operating systems, except on
the largest projects. You probably do not need to adjust this value.</p>
<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
</dd>
<dt>
core.deltaBaseCacheLimit
</dt>
<dd>
<p>
Maximum number of bytes to reserve for caching base objects
that multiple deltafied objects reference. By storing the
entire decompressed base objects in a cache Git is able
to avoid unpacking and decompressing frequently used base
objects multiple times.
</p>
<p>Default is 16 MiB on all platforms. This should be reasonable
for all users/operating systems, except on the largest projects.
You probably do not need to adjust this value.</p>
<p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p>
</dd>
<dt>
alias.*
</dt>
<dd>
<p>
Command aliases for the <a href="git.html">git(1)</a> command wrapper - e.g.
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
spaces, the usual shell quoting and escaping is supported.
quote pair and a backslash can be used to quote them.
</p>
<div class="literalblock">
<div class="content">
<pre><tt>If the alias expansion is prefixed with an exclamation point,
it will be treated as a shell command. For example, defining
"alias.new = !gitk --all --not ORIG_HEAD", the invocation
"git new" is equivalent to running the shell command
"gitk --all --not ORIG_HEAD".</tt></pre>
</div></div>
</dd>
<dt>
apply.whitespace
</dt>
<dd>
<p>
Tells <tt>git-apply</tt> how to handle whitespaces, in the same way
as the <em>--whitespace</em> option. See <a href="git-apply.html">git-apply(1)</a>.
</p>
</dd>
<dt>
branch.&lt;name&gt;.remote
</dt>
<dd>
<p>
When in branch &lt;name&gt;, it tells <tt>git fetch</tt> which remote to fetch.
If this option is not given, <tt>git fetch</tt> defaults to remote "origin".
</p>
</dd>
<dt>
branch.&lt;name&gt;.merge
</dt>
<dd>
<p>
When in branch &lt;name&gt;, it tells <tt>git fetch</tt> the default refspec to
be marked for merging in FETCH_HEAD. The value has exactly to match
a remote part of one of the refspecs which are fetched from the remote
given by "branch.&lt;name&gt;.remote".
The merge information is used by <tt>git pull</tt> (which at first calls
<tt>git fetch</tt>) to lookup the default branch for merging. Without
this option, <tt>git pull</tt> defaults to merge the first refspec fetched.
Specify multiple values to get an octopus merge.
If you wish to setup <tt>git pull</tt> so that it merges into &lt;name&gt; from
another branch in the local repository, you can point
branch.&lt;name&gt;.merge to the desired branch, and use the special setting
<tt>.</tt> (a period) for branch.&lt;name&gt;.remote.
</p>
</dd>
<dt>
clean.requireForce
</dt>
<dd>
<p>
A boolean to make git-clean do nothing unless given -f or -n. Defaults
to false.
</p>
</dd>
<dt>
color.branch
</dt>
<dd>
<p>
A boolean to enable/disable color in the output of
<a href="git-branch.html">git-branch(1)</a>. May be set to <tt>true</tt> (or <tt>always</tt>),
<tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt>, in which case colors are used
only when the output is to a terminal. Defaults to false.
</p>
</dd>
<dt>
color.branch.&lt;slot&gt;
</dt>
<dd>
<p>
Use customized color for branch coloration. <tt>&lt;slot&gt;</tt> is one of
<tt>current</tt> (the current branch), <tt>local</tt> (a local branch),
<tt>remote</tt> (a tracking branch in refs/remotes/), <tt>plain</tt> (other
refs).
</p>
<p>The value for these configuration variables is a list of colors (at most
two) and attributes (at most one), separated by spaces. The colors
accepted are <tt>normal</tt>, <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>,
<tt>magenta</tt>, <tt>cyan</tt> and <tt>white</tt>; the attributes are <tt>bold</tt>, <tt>dim</tt>, <tt>ul</tt>,
<tt>blink</tt> and <tt>reverse</tt>. The first color given is the foreground; the
second is the background. The position of the attribute, if any,
doesn't matter.</p>
</dd>
<dt>
color.diff
</dt>
<dd>
<p>
When true (or <tt>always</tt>), always use colors in patch.
When false (or <tt>never</tt>), never. When set to <tt>auto</tt>, use
colors only when the output is to the terminal.
</p>
</dd>
<dt>
color.diff.&lt;slot&gt;
</dt>
<dd>
<p>
Use customized color for diff colorization. <tt>&lt;slot&gt;</tt> specifies
which part of the patch to use the specified color, and is one
of <tt>plain</tt> (context text), <tt>meta</tt> (metainformation), <tt>frag</tt>
(hunk header), <tt>old</tt> (removed lines), <tt>new</tt> (added lines),
<tt>commit</tt> (commit headers), or <tt>whitespace</tt> (highlighting dubious
whitespace). The values of these variables may be specified as
in color.branch.&lt;slot&gt;.
</p>
</dd>
<dt>
color.pager
</dt>
<dd>
<p>
A boolean to enable/disable colored output when the pager is in
use (default is true).
</p>
</dd>
<dt>
color.status
</dt>
<dd>
<p>
A boolean to enable/disable color in the output of
<a href="git-status.html">git-status(1)</a>. May be set to <tt>true</tt> (or <tt>always</tt>),
<tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt>, in which case colors are used
only when the output is to a terminal. Defaults to false.
</p>
</dd>
<dt>
color.status.&lt;slot&gt;
</dt>
<dd>
<p>
Use customized color for status colorization. <tt>&lt;slot&gt;</tt> is
one of <tt>header</tt> (the header text of the status message),
<tt>added</tt> or <tt>updated</tt> (files which are added but not committed),
<tt>changed</tt> (files which are changed but not added in the index),
or <tt>untracked</tt> (files which are not tracked by git). The values of
these variables may be specified as in color.branch.&lt;slot&gt;.
</p>
</dd>
<dt>
diff.renameLimit
</dt>
<dd>
<p>
The number of files to consider when performing the copy/rename
detection; equivalent to the git diff option <em>-l</em>.
</p>
</dd>
<dt>
diff.renames
</dt>
<dd>
<p>
Tells git to detect renames. If set to any boolean value, it
will enable basic rename detection. If set to "copies" or
"copy", it will detect copies, as well.
</p>
</dd>
<dt>
fetch.unpackLimit
</dt>
<dd>
<p>
If the number of objects fetched over the git native
transfer is below this
limit, then the objects will be unpacked into loose object
files. However if the number of received objects equals or
exceeds this limit then the received pack will be stored as
a pack, after adding any missing delta bases. Storing the
pack from a push can make the push operation complete faster,
especially on slow filesystems.
</p>
</dd>
<dt>
format.headers
</dt>
<dd>
<p>
Additional email headers to include in a patch to be submitted
by mail. See <a href="git-format-patch.html">git-format-patch(1)</a>.
</p>
</dd>
<dt>
format.suffix
</dt>
<dd>
<p>
The default for format-patch is to output files with the suffix
<tt>.patch</tt>. Use this variable to change that suffix (make sure to
include the dot if you want it).
</p>
</dd>
<dt>
gc.packrefs
</dt>
<dd>
<p>
<tt>git gc</tt> does not run <tt>git pack-refs</tt> in a bare repository by
default so that older dumb-transport clients can still fetch
from the repository. Setting this to <tt>true</tt> lets <tt>git
gc</tt> to run <tt>git pack-refs</tt>. Setting this to <tt>false</tt> tells
<tt>git gc</tt> never to run <tt>git pack-refs</tt>. The default setting is
<tt>notbare</tt>. Enable it only when you know you do not have to
support such clients. The default setting will change to <tt>true</tt>
at some stage, and setting this to <tt>false</tt> will continue to
prevent <tt>git pack-refs</tt> from being run from <tt>git gc</tt>.
</p>
</dd>
<dt>
gc.reflogexpire
</dt>
<dd>
<p>
<tt>git reflog expire</tt> removes reflog entries older than
this time; defaults to 90 days.
</p>
</dd>
<dt>
gc.reflogexpireunreachable
</dt>
<dd>
<p>
<tt>git reflog expire</tt> removes reflog entries older than
this time and are not reachable from the current tip;
defaults to 30 days.
</p>
</dd>
<dt>
gc.rerereresolved
</dt>
<dd>
<p>
Records of conflicted merge you resolved earlier are
kept for this many days when <tt>git rerere gc</tt> is run.
The default is 60 days. See <a href="git-rerere.html">git-rerere(1)</a>.
</p>
</dd>
<dt>
gc.rerereunresolved
</dt>
<dd>
<p>
Records of conflicted merge you have not resolved are
kept for this many days when <tt>git rerere gc</tt> is run.
The default is 15 days. See <a href="git-rerere.html">git-rerere(1)</a>.
</p>
</dd>
<dt>
gitcvs.enabled
</dt>
<dd>
<p>
Whether the cvs server interface is enabled for this repository.
See <a href="git-cvsserver.html">git-cvsserver(1)</a>.
</p>
</dd>
<dt>
gitcvs.logfile
</dt>
<dd>
<p>
Path to a log file where the cvs server interface well&#8230; logs
various stuff. See <a href="git-cvsserver.html">git-cvsserver(1)</a>.
</p>
</dd>
<dt>
gitcvs.allbinary
</dt>
<dd>
<p>
If true, all files are sent to the client in mode <em>-kb</em>. This
causes the client to treat all files as binary files which suppresses
any newline munging it otherwise might do. A work-around for the
fact that there is no way yet to set single files to mode <em>-kb</em>.
</p>
</dd>
<dt>
gitcvs.dbname
</dt>
<dd>
<p>
Database used by git-cvsserver to cache revision information
derived from the git 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
<a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<tt>;</tt>).
Default: <em>%Ggitcvs.%m.sqlite</em>
</p>
</dd>
<dt>
gitcvs.dbdriver
</dt>
<dd>
<p>
Used Perl DBI driver. You can specify any available driver
for this here, but it might not work. git-cvsserver is tested
with <em>DBD::SQLite</em>, reported to work with <em>DBD::Pg</em>, and
reported <strong>not</strong> to work with <em>DBD::mysql</em>. Experimental feature.
May not contain double colons (<tt>:</tt>). Default: <em>SQLite</em>.
See <a href="git-cvsserver.html">git-cvsserver(1)</a>.
</p>
</dd>
<dt>
gitcvs.dbuser, gitcvs.dbpass
</dt>
<dd>
<p>
Database user and password. Only useful if setting <em>gitcvs.dbdriver</em>,
since SQLite has no concept of database users and/or passwords.
<em>gitcvs.dbuser</em> supports variable substitution (see
<a href="git-cvsserver.html">git-cvsserver(1)</a> for details).
</p>
</dd>
</dl>
<p>All gitcvs variables except for <em>gitcvs.allbinary</em> can also specifed
as <em>gitcvs.&lt;access_method&gt;.&lt;varname&gt;</em> (where <em>access_method</em> is one
of "ext" and "pserver") to make them apply only for the given access
method.</p>
<dl>
<dt>
http.sslVerify
</dt>
<dd>
<p>
Whether to verify the SSL certificate when fetching or pushing
over HTTPS. Can be overridden by the <em>GIT_SSL_NO_VERIFY</em> environment
variable.
</p>
</dd>
<dt>
http.sslCert
</dt>
<dd>
<p>
File containing the SSL certificate when fetching or pushing
over HTTPS. Can be overridden by the <em>GIT_SSL_CERT</em> environment
variable.
</p>
</dd>
<dt>
http.sslKey
</dt>
<dd>
<p>
File containing the SSL private key when fetching or pushing
over HTTPS. Can be overridden by the <em>GIT_SSL_KEY</em> environment
variable.
</p>
</dd>
<dt>
http.sslCAInfo
</dt>
<dd>
<p>
File containing the certificates to verify the peer with when
fetching or pushing over HTTPS. Can be overridden by the
<em>GIT_SSL_CAINFO</em> environment variable.
</p>
</dd>
<dt>
http.sslCAPath
</dt>
<dd>
<p>
Path containing files with the CA certificates to verify the peer
with when fetching or pushing over HTTPS. Can be overridden
by the <em>GIT_SSL_CAPATH</em> environment variable.
</p>
</dd>
<dt>
http.maxRequests
</dt>
<dd>
<p>
How many HTTP requests to launch in parallel. Can be overridden
by the <em>GIT_HTTP_MAX_REQUESTS</em> environment variable. Default is 5.
</p>
</dd>
<dt>
http.lowSpeedLimit, http.lowSpeedTime
</dt>
<dd>
<p>
If the HTTP transfer speed is less than <em>http.lowSpeedLimit</em>
for longer than <em>http.lowSpeedTime</em> seconds, the transfer is aborted.
Can be overridden by the <em>GIT_HTTP_LOW_SPEED_LIMIT</em> and
<em>GIT_HTTP_LOW_SPEED_TIME</em> environment variables.
</p>
</dd>
<dt>
http.noEPSV
</dt>
<dd>
<p>
A boolean which disables using of EPSV ftp command by curl.
This can helpful with some "poor" ftp servers which don't
support EPSV mode. Can be overridden by the <em>GIT_CURL_FTP_NO_EPSV</em>
environment variable. Default is false (curl will use EPSV).
</p>
</dd>
<dt>
i18n.commitEncoding
</dt>
<dd>
<p>
Character encoding the commit messages are stored in; git 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
porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
</p>
</dd>
<dt>
i18n.logOutputEncoding
</dt>
<dd>
<p>
Character encoding the commit messages are converted to when
running <tt>git-log</tt> and friends.
</p>
</dd>
<dt>
log.showroot
</dt>
<dd>
<p>
If true, the initial commit will be shown as a big creation event.
This is equivalent to a diff against an empty tree.
Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
normally hide the root commit will now show it. True by default.
</p>
</dd>
<dt>
merge.summary
</dt>
<dd>
<p>
Whether to include summaries of merged commits in newly created
merge commit messages. False by default.
</p>
</dd>
<dt>
merge.tool
</dt>
<dd>
<p>
Controls which merge resolution program is used by
<a href="git-mergetool.html">git-mergetool(l)</a>. Valid values are: "kdiff3", "tkdiff",
"meld", "xxdiff", "emerge", "vimdiff", and "opendiff"
</p>
</dd>
<dt>
merge.verbosity
</dt>
<dd>
<p>
Controls the amount of output shown by the recursive merge
strategy. Level 0 outputs nothing except a final error
message if conflicts were detected. Level 1 outputs only
conflicts, 2 outputs conflicts and file changes. Level 5 and
above outputs debugging information. The default is level 2.
</p>
</dd>
<dt>
merge.&lt;driver&gt;.name
</dt>
<dd>
<p>
Defines a human readable name for a custom low-level
merge driver. See <a href="gitattributes.html">gitattributes(5)</a> for details.
</p>
</dd>
<dt>
merge.&lt;driver&gt;.driver
</dt>
<dd>
<p>
Defines the command that implements a custom low-level
merge driver. See <a href="gitattributes.html">gitattributes(5)</a> for details.
</p>
</dd>
<dt>
merge.&lt;driver&gt;.recursive
</dt>
<dd>
<p>
Names a low-level merge driver to be used when
performing an internal merge between common ancestors.
See <a href="gitattributes.html">gitattributes(5)</a> for details.
</p>
</dd>
<dt>
pack.window
</dt>
<dd>
<p>
The size of the window used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
window size is given on the command line. Defaults to 10.
</p>
</dd>
<dt>
pull.octopus
</dt>
<dd>
<p>
The default merge strategy to use when pulling multiple branches
at once.
</p>
</dd>
<dt>
pull.twohead
</dt>
<dd>
<p>
The default merge strategy to use when pulling a single branch.
</p>
</dd>
<dt>
remote.&lt;name&gt;.url
</dt>
<dd>
<p>
The URL of a remote repository. See <a href="git-fetch.html">git-fetch(1)</a> or
<a href="git-push.html">git-push(1)</a>.
</p>
</dd>
<dt>
remote.&lt;name&gt;.fetch
</dt>
<dd>
<p>
The default set of "refspec" for <a href="git-fetch.html">git-fetch(1)</a>. See
<a href="git-fetch.html">git-fetch(1)</a>.
</p>
</dd>
<dt>
remote.&lt;name&gt;.push
</dt>
<dd>
<p>
The default set of "refspec" for <a href="git-push.html">git-push(1)</a>. See
<a href="git-push.html">git-push(1)</a>.
</p>
</dd>
<dt>
remote.&lt;name&gt;.skipDefaultUpdate
</dt>
<dd>
<p>
If true, this remote will be skipped by default when updating
using the remote subcommand of <a href="git-remote.html">git-remote(1)</a>.
</p>
</dd>
<dt>
remote.&lt;name&gt;.receivepack
</dt>
<dd>
<p>
The default program to execute on the remote side when pushing. See
option --exec of <a href="git-push.html">git-push(1)</a>.
</p>
</dd>
<dt>
remote.&lt;name&gt;.uploadpack
</dt>
<dd>
<p>
The default program to execute on the remote side when fetching. See
option --exec of <a href="git-fetch-pack.html">git-fetch-pack(1)</a>.
</p>
</dd>
<dt>
remote.&lt;name&gt;.tagopt
</dt>
<dd>
<p>
Setting this value to --no-tags disables automatic tag following when fetching
from remote &lt;name&gt;
</p>
</dd>
<dt>
remotes.&lt;group&gt;
</dt>
<dd>
<p>
The list of remotes which are fetched by "git remote update
&lt;group&gt;". See <a href="git-remote.html">git-remote(1)</a>.
</p>
</dd>
<dt>
repack.usedeltabaseoffset
</dt>
<dd>
<p>
Allow <a href="git-repack.html">git-repack(1)</a> to create packs that uses
delta-base offset. Defaults to false.
</p>
</dd>
<dt>
show.difftree
</dt>
<dd>
<p>
The default <a href="git-diff-tree.html">git-diff-tree(1)</a> arguments to be used
for <a href="git-show.html">git-show(1)</a>.
</p>
</dd>
<dt>
showbranch.default
</dt>
<dd>
<p>
The default set of branches for <a href="git-show-branch.html">git-show-branch(1)</a>.
See <a href="git-show-branch.html">git-show-branch(1)</a>.
</p>
</dd>
<dt>
tar.umask
</dt>
<dd>
<p>
By default, <a href="git-tar-tree.html">git-tar-tree(1)</a> sets file and directories modes
to 0666 or 0777. While this is both useful and acceptable for projects
such as the Linux Kernel, it might be excessive for other projects.
With this variable, it becomes possible to tell
<a href="git-tar-tree.html">git-tar-tree(1)</a> to apply a specific umask to the modes above.
The special value "user" indicates that the user's current umask will
be used. This should be enough for most projects, as it will lead to
the same permissions as <a href="git-checkout.html">git-checkout(1)</a> would use. The default
value remains 0, which means world read-write.
</p>
</dd>
<dt>
user.email
</dt>
<dd>
<p>
Your email address to be recorded in any newly created commits.
Can be overridden by the <em>GIT_AUTHOR_EMAIL</em>, <em>GIT_COMMITTER_EMAIL</em>, and
<em>EMAIL</em> environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
</p>
</dd>
<dt>
user.name
</dt>
<dd>
<p>
Your full name to be recorded in any newly created commits.
Can be overridden by the <em>GIT_AUTHOR_NAME</em> and <em>GIT_COMMITTER_NAME</em>
environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
</p>
</dd>
<dt>
user.signingkey
</dt>
<dd>
<p>
If <a href="git-tag.html">git-tag(1)</a> is not selecting the key you want it to
automatically when creating a signed tag, you can override the
default selection with this variable. This option is passed
unchanged to gpg's --local-user parameter, so you may specify a key
using any method that gpg supports.
</p>
</dd>
<dt>
whatchanged.difftree
</dt>
<dd>
<p>
The default <a href="git-diff-tree.html">git-diff-tree(1)</a> arguments to be used
for <a href="git-whatchanged.html">git-whatchanged(1)</a>.
</p>
</dd>
<dt>
imap
</dt>
<dd>
<p>
The configuration variables in the <em>imap</em> section are described
in <a href="git-imap-send.html">git-imap-send(1)</a>.
</p>
</dd>
<dt>
receive.unpackLimit
</dt>
<dd>
<p>
If the number of objects received in a push is below this
limit then the objects will be unpacked into loose object
files. However if the number of received objects equals or
exceeds this limit then the received pack will be stored as
a pack, after adding any missing delta bases. Storing the
pack from a push can make the push operation complete faster,
especially on slow filesystems.
</p>
</dd>
<dt>
receive.denyNonFastForwards
</dt>
<dd>
<p>
If set to true, git-receive-pack will deny a ref update which is
not a fast forward. Use this to prevent such an update via a push,
even if that push is forced. This configuration variable is
set when initializing a shared repository.
</p>
</dd>
<dt>
transfer.unpackLimit
</dt>
<dd>
<p>
When <tt>fetch.unpackLimit</tt> or <tt>receive.unpackLimit</tt> are
not set, the value of this variable is used instead.
</p>
</dd>
</dl>
</div>
<h2>Author</h2>
<div class="sectionbody">
<p>Written by Johannes Schindelin &lt;Johannes.Schindelin@gmx.de&gt;</p>
</div>
<h2>Documentation</h2>
<div class="sectionbody">
<p>Documentation by Johannes Schindelin, Petr Baudis and the git-list &lt;git@vger.kernel.org&gt;.</p>
</div>
<h2>GIT</h2>
<div class="sectionbody">
<p>Part of the <a href="git.html">git(7)</a> suite</p>
</div>
<div id="footer">
<div id="footer-text">
Last updated 04-May-2007 07:07:21 UTC
</div>
</div>
</body>
</html>