+<h2>CONFIGURATION FILE</h2>\r
+<div class="sectionbody">\r
+<p>The git configuration file contains a number of variables that affect\r
+the git commands behaviour. They can be used by both the git plumbing\r
+and the porcelains. The variables are divided to sections, where\r
+in the fully qualified variable name the variable itself is the last\r
+dot-separated segment and the section name is everything before the last\r
+dot. The variable names are case-insensitive and only alphanumeric\r
+characters are allowed. Some variables may appear multiple times.</p>\r
+<p>The syntax is fairly flexible and permissive; whitespaces are mostly\r
+ignored. The <em>#</em> and <em>;</em> characters begin commends to the end of line,\r
+blank lines are ignored, lines containing strings enclosed in square\r
+brackets start sections and all the other lines are recognized\r
+as setting variables, in the form <em>name = value</em>. If there is no equal\r
+sign on the line, the entire line is taken as <em>name</em> and the variable\r
+is recognized as boolean "true". String values may be entirely or partially\r
+enclosed in double quotes; some variables may require special value format.</p>\r
+<h3>Example</h3>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt># Core variables\r
+[core]\r
+ ; Don't trust file modes\r
+ filemode = false</tt></pre>\r
+</div></div>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt># Our diff algorithm\r
+[diff]\r
+ external = "/usr/local/bin/gnu-diff -u"\r
+ renames = true</tt></pre>\r
+</div></div>\r
+<h3>Variables</h3>\r
+<p>Note that this list is non-comprehensive and not necessarily complete.\r
+For command-specific variables, you will find more detailed description\r
+in the appropriate manual page. You will find description of non-core\r
+porcelain configuration variables in the respective porcelain documentation.</p>\r
+<dl>\r
+<dt>\r
+core.fileMode\r
+</dt>\r
+<dd>\r
+<p>\r
+ If false, the executable bit differences between the index and\r
+ the working copy are ignored; useful on broken filesystems like FAT.\r
+ See <a href="git-update-index.html">git-update-index(1)</a>. True by default.\r
+</p>\r
+</dd>\r
+<dt>\r
+core.gitProxy\r
+</dt>\r
+<dd>\r
+<p>\r
+ A "proxy command" to execute (as <em>command host port</em>) instead\r
+ of establishing direct connection to the remote server when\r
+ using the git protocol for fetching. If the variable value is\r
+ in the "COMMAND for DOMAIN" format, the command is applied only\r
+ on hostnames ending with the specified domain string. This variable\r
+ may be set multiple times and is matched in the given order;\r
+ the first match wins.\r
+</p>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt>Can be overriden by the 'GIT_PROXY_COMMAND' environment variable\r
+(which always applies universally, without the special "for"\r
+handling).</tt></pre>\r
+</div></div>\r
+</dd>\r
+<dt>\r
+core.ignoreStat\r
+</dt>\r
+<dd>\r
+<p>\r
+ The working copy files are assumed to stay unchanged until you\r
+ mark them otherwise manually - Git will not detect the file changes\r
+ by lstat() calls. This is useful on systems where those are very\r
+ slow, such as Microsoft Windows. See <a href="git-update-index.html">git-update-index(1)</a>.\r
+ False by default.\r
+</p>\r
+</dd>\r
+<dt>\r
+core.onlyUseSymrefs\r
+</dt>\r
+<dd>\r
+<p>\r
+ Always use the "symref" format instead of symbolic links for HEAD\r
+ and other symbolic reference files. True by default.\r
+</p>\r
+</dd>\r
+<dt>\r
+core.repositoryFormatVersion\r
+</dt>\r
+<dd>\r
+<p>\r
+ Internal variable identifying the repository format and layout\r
+ version.\r
+</p>\r
+</dd>\r
+<dt>\r
+core.sharedRepository\r
+</dt>\r
+<dd>\r
+<p>\r
+ If true, the repository is made shareable between several users\r
+ in a group (making sure all the files and objects are group-writable).\r
+ See <a href="git-init-db.html">git-init-db(1)</a>. False by default.\r
+</p>\r
+</dd>\r
+<dt>\r
+core.warnAmbiguousRefs\r
+</dt>\r
+<dd>\r
+<p>\r
+ If true, git will warn you if the ref name you passed it is ambiguous\r
+ and might match multiple refs in the .git/refs/ tree. True by default.\r
+</p>\r
+</dd>\r
+<dt>\r
+apply.whitespace\r
+</dt>\r
+<dd>\r
+<p>\r
+ Tells <tt>git-apply</tt> how to handle whitespaces, in the same way\r
+ as the <em>--whitespace</em> option. See <a href="git-apply.html">git-apply(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+diff.renameLimit\r
+</dt>\r
+<dd>\r
+<p>\r
+ The number of files to consider when performing the copy/rename\r
+ detection; equivalent to the git diff option <em>-l</em>.\r
+</p>\r
+</dd>\r
+<dt>\r
+format.headers\r
+</dt>\r
+<dd>\r
+<p>\r
+ Additional email headers to include in a patch to be submitted\r
+ by mail. See <a href="git-format-patch.html">git-format-patch(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+gitcvs.enabled\r
+</dt>\r
+<dd>\r
+<p>\r
+ Whether the cvs pserver interface is enabled for this repository.\r
+ See <a href="git-cvsserver.html">git-cvsserver(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+gitcvs.logfile\r
+</dt>\r
+<dd>\r
+<p>\r
+ Path to a log file where the cvs pserver interface well… logs\r
+ various stuff. See <a href="git-cvsserver.html">git-cvsserver(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+http.sslVerify\r
+</dt>\r
+<dd>\r
+<p>\r
+ Whether to verify the SSL certificate when fetching or pushing\r
+ over HTTPS. Can be overriden by the <em>GIT_SSL_NO_VERIFY</em> environment\r
+ variable.\r
+</p>\r
+</dd>\r
+<dt>\r
+http.sslCert\r
+</dt>\r
+<dd>\r
+<p>\r
+ File containing the SSL certificate when fetching or pushing\r
+ over HTTPS. Can be overriden by the <em>GIT_SSL_CERT</em> environment\r
+ variable.\r
+</p>\r
+</dd>\r
+<dt>\r
+http.sslKey\r
+</dt>\r
+<dd>\r
+<p>\r
+ File containing the SSL private key when fetching or pushing\r
+ over HTTPS. Can be overriden by the <em>GIT_SSL_KEY</em> environment\r
+ variable.\r
+</p>\r
+</dd>\r
+<dt>\r
+http.sslCAInfo\r
+</dt>\r
+<dd>\r
+<p>\r
+ File containing the certificates to verify the peer with when\r
+ fetching or pushing over HTTPS. Can be overriden by the\r
+ <em>GIT_SSL_CAINFO</em> environment variable.\r
+</p>\r
+</dd>\r
+<dt>\r
+http.sslCAPath\r
+</dt>\r
+<dd>\r
+<p>\r
+ Path containing files with the CA certificates to verify the peer\r
+ with when fetching or pushing over HTTPS. Can be overriden\r
+ by the <em>GIT_SSL_CAPATH</em> environment variable.\r
+</p>\r
+</dd>\r
+<dt>\r
+http.maxRequests\r
+</dt>\r
+<dd>\r
+<p>\r
+ How many HTTP requests to launch in parallel. Can be overriden\r
+ by the <em>GIT_HTTP_MAX_REQUESTS</em> environment variable. Default is 5.\r
+</p>\r
+</dd>\r
+<dt>\r
+http.lowSpeedLimit, http.lowSpeedTime\r
+</dt>\r
+<dd>\r
+<p>\r
+ If the HTTP transfer speed is less than <em>http.lowSpeedLimit</em>\r
+ for longer than <em>http.lowSpeedTime</em> seconds, the transfer is aborted.\r
+ Can be overriden by the <em>GIT_HTTP_LOW_SPEED_LIMIT</em> and\r
+ <em>GIT_HTTP_LOW_SPEED_TIME</em> environment variables.\r
+</p>\r
+</dd>\r
+<dt>\r
+i18n.commitEncoding\r
+</dt>\r
+<dd>\r
+<p>\r
+ Character encoding the commit messages are stored in; git itself\r
+ does not care per se, but this information is necessary e.g. when\r
+ importing commits from emails or in the gitk graphical history\r
+ browser (and possibly at other places in the future or in other\r
+ porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.\r
+</p>\r
+</dd>\r
+<dt>\r
+merge.summary\r
+</dt>\r
+<dd>\r
+<p>\r
+ Whether to include summaries of merged commits in newly created\r
+ merge commit messages. False by default.\r
+</p>\r
+</dd>\r
+<dt>\r
+pull.octopus\r
+</dt>\r
+<dd>\r
+<p>\r
+ The default merge strategy to use when pulling multiple branches\r
+ at once.\r
+</p>\r
+</dd>\r
+<dt>\r
+pull.twohead\r
+</dt>\r
+<dd>\r
+<p>\r
+ The default merge strategy to use when pulling a single branch.\r
+</p>\r
+</dd>\r
+<dt>\r
+show.difftree\r
+</dt>\r
+<dd>\r
+<p>\r
+ The default <a href="git-diff-tree.html">git-diff-tree(1)</a> arguments to be used\r
+ for <a href="git-show.html">git-show(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+showbranch.default\r
+</dt>\r
+<dd>\r
+<p>\r
+ The default set of branches for <a href="git-show-branch.html">git-show-branch(1)</a>.\r
+ See <a href="git-show-branch.html">git-show-branch(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+user.email\r
+</dt>\r
+<dd>\r
+<p>\r
+ Your email address to be recorded in any newly created commits.\r
+ Can be overriden by the <em>GIT_AUTHOR_EMAIL</em> and <em>GIT_COMMITTER_EMAIL</em>\r
+ environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+user.name\r
+</dt>\r
+<dd>\r
+<p>\r
+ Your full name to be recorded in any newly created commits.\r
+ Can be overriden by the <em>GIT_AUTHOR_NAME</em> and <em>GIT_COMMITTER_NAME</em>\r
+ environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+whatchanged.difftree\r
+</dt>\r
+<dd>\r
+<p>\r
+ The default <a href="git-diff-tree.html">git-diff-tree(1)</a> arguments to be used\r
+ for <a href="git-whatchanged.html">git-whatchanged(1)</a>.\r
+</p>\r
+</dd>\r
+<dt>\r
+imap\r
+</dt>\r
+<dd>\r
+<p>\r
+ The configuration variables in the <em>imap</em> section are described\r
+ in <a href="git-imap-send.html">git-imap-send(1)</a>.\r
+</p>\r
+</dd>\r
+</dl>\r
+</div>\r