blob: f6bcb40d7ebc4771bb79b6f2ef6a004ea41628dd [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-repo-config(1)</title>
</head>
<body>
<div id="header">
<h1>
git-repo-config(1) Manual Page
</h1>
<h2>NAME</h2>
<div class="sectionbody">
<p>git-repo-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-repo-config</em> [--global] [type] name [value [value_regex]]
<em>git-repo-config</em> [--global] [type] --replace-all name [value [value_regex]]
<em>git-repo-config</em> [--global] [type] --get name [value_regex]
<em>git-repo-config</em> [--global] [type] --get-all name [value_regex]
<em>git-repo-config</em> [--global] [type] --unset name [value_regex]
<em>git-repo-config</em> [--global] [type] --unset-all name [value_regex]
<em>git-repo-config</em> [--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>If you want to set/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-repo-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>
--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>
--unset
</dt>
<dd>
<p>
Remove the line matching the key from config file.
</p>
</dd>
<dt>
--unset-all
</dt>
<dd>
<p>
Remove all matching lines 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-repo-config will ensure that the output is "true" or "false"
</p>
</dd>
<dt>
--int
</dt>
<dd>
<p>
git-repo-config will ensure that the output is a simple decimal number
</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 repo-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 repo-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 repo-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 repo-config --get core.filemode</tt></pre>
</div></div>
<p>or</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git repo-config core.filemode</tt></pre>
</div></div>
<p>or, to query a multivar:</p>
<div class="listingblock">
<div class="content">
<pre><tt>% git repo-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 repo-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 repo-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 repo-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 repo-config section.key value '[!]'</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. 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>
<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, lines containing strings enclosed in square
brackets start sections and 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". String values may be entirely or partially
enclosed in double quotes; 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>
<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.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.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>
<div class="literalblock">
<div class="content">
<pre><tt>This information can be used to determine what commit
was the tip of a branch "2 days ago". This value is
false by default (no automated creation of log files).</tt></pre>
</div></div>
</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-db.html">git-init-db(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 enables the legacy object header format in case
you want to interoperate with old clients accessing the object
database directly (where the "http://" and "rsync://" protocols
count as direct access).
</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>
</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.
</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 remote branch
to be merged.
</p>
</dd>
<dt>
pager.color
</dt>
<dd>
<p>
A boolean to enable/disable colored output when the pager is in
use (default is true).
</p>
</dd>
<dt>
diff.color
</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>
diff.color.&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), or <tt>new</tt> (added lines). The value for these
configuration variables can be one of: <tt>normal</tt>, <tt>bold</tt>,
<tt>dim</tt>, <tt>ul</tt>, <tt>blink</tt>, <tt>reverse</tt>, <tt>reset</tt>, <tt>black</tt>,
<tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>, <tt>magenta</tt>, <tt>cyan</tt>, or
<tt>white</tt>.
</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>
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>
gitcvs.enabled
</dt>
<dd>
<p>
Whether the cvs pserver 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 pserver interface well&#8230; logs
various stuff. See <a href="git-cvsserver.html">git-cvsserver(1)</a>.
</p>
</dd>
<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 doesn'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>
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>
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>
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>
status.color
</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>
status.color.&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>updated</tt> (files which are updated but not committed),
<tt>changed</tt> (files which are changed but not updated in the index),
or <tt>untracked</tt> (files which are not tracked by git). The values of
these variables may be specified as in diff.color.&lt;slot&gt;.
</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> and <em>GIT_COMMITTER_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>
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>
</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 29-Nov-2006 20:39:59 UTC
</div>
</div>
</body>
</html>