Documentation/config.txt

   1 CONFIGURATION FILE
   2 ------------------
   3
   4 The git configuration file contains a number of variables that affect
   5 the git command's behavior. `.git/config` file for each repository
   6 is used to store the information for that repository, and
   7 `$HOME/.gitconfig` is used to store per user information to give
   8 fallback values for `.git/config` file. The file `/etc/gitconfig`
   9 can be used to store system-wide defaults.
  10
  11 They can be used by both the git plumbing
  12 and the porcelains. The variables are divided into sections, where
  13 in the fully qualified variable name the variable itself is the last
  14 dot-separated segment and the section name is everything before the last
  15 dot. The variable names are case-insensitive and only alphanumeric
  16 characters are allowed. Some variables may appear multiple times.
  17
  18 Syntax
  19 ~~~~~~
  20
  21 The syntax is fairly flexible and permissive; whitespaces are mostly
  22 ignored.  The '#' and ';' characters begin comments to the end of line,
  23 blank lines are ignored.
  24
  25 The file consists of sections and variables.  A section begins with
  26 the name of the section in square brackets and continues until the next
  27 section begins.  Section names are not case sensitive.  Only alphanumeric
  28 characters, '`-`' and '`.`' are allowed in section names.  Each variable
  29 must belong to some section, which means that there must be section
  30 header before first setting of a variable.
  31
  32 Sections can be further divided into subsections.  To begin a subsection
  33 put its name in double quotes, separated by space from the section name,
  34 in the section header, like in example below:
  35
  36 --------
  37         [section "subsection"]
  38
  39 --------
  40
  41 Subsection names can contain any characters except newline (doublequote
  42 '`"`' and backslash have to be escaped as '`\"`' and '`\\`',
  43 respectively) and are case sensitive.  Section header cannot span multiple
  44 lines.  Variables may belong directly to a section or to a given subsection.
  45 You can have `[section]` if you have `[section "subsection"]`, but you
  46 don't need to.
  47
  48 There is also (case insensitive) alternative `[section.subsection]` syntax.
  49 In this syntax subsection names follow the same restrictions as for section
  50 name.
  51
  52 All the other lines are recognized as setting variables, in the form
  53 'name = value'.  If there is no equal sign on the line, the entire line
  54 is taken as 'name' and the variable is recognized as boolean "true".
  55 The variable names are case-insensitive and only alphanumeric
  56 characters and '`-`' are allowed.  There can be more than one value
  57 for a given variable; we say then that variable is multivalued.
  58
  59 Leading and trailing whitespace in a variable value is discarded.
  60 Internal whitespace within a variable value is retained verbatim.
  61
  62 The values following the equals sign in variable assign are all either
  63 a string, an integer, or a boolean.  Boolean values may be given as yes/no,
  64 0/1 or true/false.  Case is not significant in boolean values, when
  65 converting value to the canonical form using '--bool' type specifier;
  66 `git-config` will ensure that the output is "true" or "false".
  67
  68 String values may be entirely or partially enclosed in double quotes.
  69 You need to enclose variable value in double quotes if you want to
  70 preserve leading or trailing whitespace, or if variable value contains
  71 beginning of comment characters (if it contains '#' or ';').
  72 Double quote '`"`' and backslash '`\`' characters in variable value must
  73 be escaped: use '`\"`' for '`"`' and '`\\`' for '`\`'.
  74
  75 The following escape sequences (beside '`\"`' and '`\\`') are recognized:
  76 '`\n`' for newline character (NL), '`\t`' for horizontal tabulation (HT, TAB)
  77 and '`\b`' for backspace (BS).  No other char escape sequence, nor octal
  78 char sequences are valid.
  79
  80 Variable value ending in a '`\`' is continued on the next line in the
  81 customary UNIX fashion.
  82
  83 Some variables may require special value format.
  84
  85 Example
  86 ~~~~~~~
  87
  88         # Core variables
  89         [core]
  90                 ; Don't trust file modes
  91                 filemode = false
  92
  93         # Our diff algorithm
  94         [diff]
  95                 external = "/usr/local/bin/gnu-diff -u"
  96                 renames = true
  97
  98         [branch "devel"]
  99                 remote = origin
 100                 merge = refs/heads/devel
 101
 102         # Proxy settings
 103         [core]
 104                 gitProxy="ssh" for "ssh://kernel.org/"
 105                 gitProxy=default-proxy ; for the rest
 106
 107 Variables
 108 ~~~~~~~~~
 109
 110 Note that this list is non-comprehensive and not necessarily complete.
 111 For command-specific variables, you will find a more detailed description
 112 in the appropriate manual page. You will find a description of non-core
 113 porcelain configuration variables in the respective porcelain documentation.
 114
 115 core.fileMode::
 116         If false, the executable bit differences between the index and
 117         the working copy are ignored; useful on broken filesystems like FAT.
 118         See gitlink:git-update-index[1]. True by default.
 119
 120 core.quotepath::
 121         The commands that output paths (e.g. `ls-files`,
 122         `diff`), when not given the `-z` option, will quote
 123         "unusual" characters in the pathname by enclosing the
 124         pathname in a double-quote pair and with backslashes the
 125         same way strings in C source code are quoted.  If this
 126         variable is set to false, the bytes higher than 0x80 are
 127         not quoted but output as verbatim.  Note that double
 128         quote, backslash and control characters are always
 129         quoted without `-z` regardless of the setting of this
 130         variable.
 131
 132 core.autocrlf::
 133         If true, makes git convert `CRLF` at the end of lines in text files to
 134         `LF` when reading from the filesystem, and convert in reverse when
 135         writing to the filesystem.  The variable can be set to
 136         'input', in which case the conversion happens only while
 137         reading from the filesystem but files are written out with
 138         `LF` at the end of lines.  Currently, which paths to consider
 139         "text" (i.e. be subjected to the autocrlf mechanism) is
 140         decided purely based on the contents.
 141
 142 core.symlinks::
 143         If false, symbolic links are checked out as small plain files that
 144         contain the link text. gitlink:git-update-index[1] and
 145         gitlink:git-add[1] will not change the recorded type to regular
 146         file. Useful on filesystems like FAT that do not support
 147         symbolic links. True by default.
 148
 149 core.gitProxy::
 150         A "proxy command" to execute (as 'command host port') instead
 151         of establishing direct connection to the remote server when
 152         using the git protocol for fetching. If the variable value is
 153         in the "COMMAND for DOMAIN" format, the command is applied only
 154         on hostnames ending with the specified domain string. This variable
 155         may be set multiple times and is matched in the given order;
 156         the first match wins.
 157 +
 158 Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
 159 (which always applies universally, without the special "for"
 160 handling).
 161
 162 core.ignoreStat::
 163         The working copy files are assumed to stay unchanged until you
 164         mark them otherwise manually - Git will not detect the file changes
 165         by lstat() calls. This is useful on systems where those are very
 166         slow, such as Microsoft Windows.  See gitlink:git-update-index[1].
 167         False by default.
 168
 169 core.preferSymlinkRefs::
 170         Instead of the default "symref" format for HEAD
 171         and other symbolic reference files, use symbolic links.
 172         This is sometimes needed to work with old scripts that
 173         expect HEAD to be a symbolic link.
 174
 175 core.bare::
 176         If true this repository is assumed to be 'bare' and has no
 177         working directory associated with it.  If this is the case a
 178         number of commands that require a working directory will be
 179         disabled, such as gitlink:git-add[1] or gitlink:git-merge[1].
 180 +
 181 This setting is automatically guessed by gitlink:git-clone[1] or
 182 gitlink:git-init[1] when the repository was created.  By default a
 183 repository that ends in "/.git" is assumed to be not bare (bare =
 184 false), while all other repositories are assumed to be bare (bare
 185 = true).
 186
 187 core.worktree::
 188         Set the path to the working tree.  The value will not be
 189         used in combination with repositories found automatically in
 190         a .git directory (i.e. $GIT_DIR is not set).
 191         This can be overriden by the GIT_WORK_TREE environment
 192         variable and the '--work-tree' command line option.
 193
 194 core.logAllRefUpdates::
 195         Updates to a ref <ref> is logged to the file
 196         "$GIT_DIR/logs/<ref>", by appending the new and old
 197         SHA1, the date/time and the reason of the update, but
 198         only when the file exists.  If this configuration
 199         variable is set to true, missing "$GIT_DIR/logs/<ref>"
 200         file is automatically created for branch heads.
 201 +
 202 This information can be used to determine what commit
 203 was the tip of a branch "2 days ago".
 204 +
 205 This value is true by default in a repository that has
 206 a working directory associated with it, and false by
 207 default in a bare repository.
 208
 209 core.repositoryFormatVersion::
 210         Internal variable identifying the repository format and layout
 211         version.
 212
 213 core.sharedRepository::
 214         When 'group' (or 'true'), the repository is made shareable between
 215         several users in a group (making sure all the files and objects are
 216         group-writable). When 'all' (or 'world' or 'everybody'), the
 217         repository will be readable by all users, additionally to being
 218         group-shareable. When 'umask' (or 'false'), git will use permissions
 219         reported by umask(2). See gitlink:git-init[1]. False by default.
 220
 221 core.warnAmbiguousRefs::
 222         If true, git will warn you if the ref name you passed it is ambiguous
 223         and might match multiple refs in the .git/refs/ tree. True by default.
 224
 225 core.compression::
 226         An integer -1..9, indicating a default compression level.
 227         -1 is the zlib default. 0 means no compression,
 228         and 1..9 are various speed/size tradeoffs, 9 being slowest.
 229
 230 core.loosecompression::
 231         An integer -1..9, indicating the compression level for objects that
 232         are not in a pack file. -1 is the zlib default. 0 means no
 233         compression, and 1..9 are various speed/size tradeoffs, 9 being
 234         slowest.  If not set,  defaults to core.compression.  If that is
 235         not set,  defaults to 0 (best speed).
 236
 237 core.packedGitWindowSize::
 238         Number of bytes of a pack file to map into memory in a
 239         single mapping operation.  Larger window sizes may allow
 240         your system to process a smaller number of large pack files
 241         more quickly.  Smaller window sizes will negatively affect
 242         performance due to increased calls to the operating system's
 243         memory manager, but may improve performance when accessing
 244         a large number of large pack files.
 245 +
 246 Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
 247 MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should
 248 be reasonable for all users/operating systems.  You probably do
 249 not need to adjust this value.
 250 +
 251 Common unit suffixes of 'k', 'm', or 'g' are supported.
 252
 253 core.packedGitLimit::
 254         Maximum number of bytes to map simultaneously into memory
 255         from pack files.  If Git needs to access more than this many
 256         bytes at once to complete an operation it will unmap existing
 257         regions to reclaim virtual address space within the process.
 258 +
 259 Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
 260 This should be reasonable for all users/operating systems, except on
 261 the largest projects.  You probably do not need to adjust this value.
 262 +
 263 Common unit suffixes of 'k', 'm', or 'g' are supported.
 264
 265 core.deltaBaseCacheLimit::
 266         Maximum number of bytes to reserve for caching base objects
 267         that multiple deltafied objects reference.  By storing the
 268         entire decompressed base objects in a cache Git is able
 269         to avoid unpacking and decompressing frequently used base
 270         objects multiple times.
 271 +
 272 Default is 16 MiB on all platforms.  This should be reasonable
 273 for all users/operating systems, except on the largest projects.
 274 You probably do not need to adjust this value.
 275 +
 276 Common unit suffixes of 'k', 'm', or 'g' are supported.
 277
 278 core.excludesfile::
 279         In addition to '.gitignore' (per-directory) and
 280         '.git/info/exclude', git looks into this file for patterns
 281         of files which are not meant to be tracked.  See
 282         gitlink:gitignore[5].
 283
 284 core.pager::
 285         The command that git will use to paginate output.  Can be overridden
 286         with the `GIT_PAGER` environment variable.
 287
 288 alias.*::
 289         Command aliases for the gitlink:git[1] command wrapper - e.g.
 290         after defining "alias.last = cat-file commit HEAD", the invocation
 291         "git last" is equivalent to "git cat-file commit HEAD". To avoid
 292         confusion and troubles with script usage, aliases that
 293         hide existing git commands are ignored. Arguments are split by
 294         spaces, the usual shell quoting and escaping is supported.
 295         quote pair and a backslash can be used to quote them.
 296
 297         If the alias expansion is prefixed with an exclamation point,
 298         it will be treated as a shell command.  For example, defining
 299         "alias.new = !gitk --all --not ORIG_HEAD", the invocation
 300         "git new" is equivalent to running the shell command
 301         "gitk --all --not ORIG_HEAD".
 302
 303 apply.whitespace::
 304         Tells `git-apply` how to handle whitespaces, in the same way
 305         as the '--whitespace' option. See gitlink:git-apply[1].
 306
 307 branch.autosetupmerge::
 308         Tells `git-branch` and `git-checkout` to setup new branches
 309         so that gitlink:git-pull[1] will appropriately merge from that
 310         remote branch.  Note that even if this option is not set,
 311         this behavior can be chosen per-branch using the `--track`
 312         and `--no-track` options.  This option defaults to false.
 313
 314 branch.<name>.remote::
 315         When in branch <name>, it tells `git fetch` which remote to fetch.
 316         If this option is not given, `git fetch` defaults to remote "origin".
 317
 318 branch.<name>.merge::
 319         When in branch <name>, it tells `git fetch` the default refspec to
 320         be marked for merging in FETCH_HEAD. The value has exactly to match
 321         a remote part of one of the refspecs which are fetched from the remote
 322         given by "branch.<name>.remote".
 323         The merge information is used by `git pull` (which at first calls
 324         `git fetch`) to lookup the default branch for merging. Without
 325         this option, `git pull` defaults to merge the first refspec fetched.
 326         Specify multiple values to get an octopus merge.
 327         If you wish to setup `git pull` so that it merges into <name> from
 328         another branch in the local repository, you can point
 329         branch.<name>.merge to the desired branch, and use the special setting
 330         `.` (a period) for branch.<name>.remote.
 331
 332 clean.requireForce::
 333         A boolean to make git-clean do nothing unless given -f or -n.  Defaults
 334         to false.
 335
 336 color.branch::
 337         A boolean to enable/disable color in the output of
 338         gitlink:git-branch[1]. May be set to `true` (or `always`),
 339         `false` (or `never`) or `auto`, in which case colors are used
 340         only when the output is to a terminal. Defaults to false.
 341
 342 color.branch.<slot>::
 343         Use customized color for branch coloration. `<slot>` is one of
 344         `current` (the current branch), `local` (a local branch),
 345         `remote` (a tracking branch in refs/remotes/), `plain` (other
 346         refs).
 347 +
 348 The value for these configuration variables is a list of colors (at most
 349 two) and attributes (at most one), separated by spaces.  The colors
 350 accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`,
 351 `magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`,
 352 `blink` and `reverse`.  The first color given is the foreground; the
 353 second is the background.  The position of the attribute, if any,
 354 doesn't matter.
 355
 356 color.diff::
 357         When true (or `always`), always use colors in patch.
 358         When false (or `never`), never.  When set to `auto`, use
 359         colors only when the output is to the terminal.
 360
 361 color.diff.<slot>::
 362         Use customized color for diff colorization.  `<slot>` specifies
 363         which part of the patch to use the specified color, and is one
 364         of `plain` (context text), `meta` (metainformation), `frag`
 365         (hunk header), `old` (removed lines), `new` (added lines),
 366         `commit` (commit headers), or `whitespace` (highlighting dubious
 367         whitespace).  The values of these variables may be specified as
 368         in color.branch.<slot>.
 369
 370 color.pager::
 371         A boolean to enable/disable colored output when the pager is in
 372         use (default is true).
 373
 374 color.status::
 375         A boolean to enable/disable color in the output of
 376         gitlink:git-status[1]. May be set to `true` (or `always`),
 377         `false` (or `never`) or `auto`, in which case colors are used
 378         only when the output is to a terminal. Defaults to false.
 379
 380 color.status.<slot>::
 381         Use customized color for status colorization. `<slot>` is
 382         one of `header` (the header text of the status message),
 383         `added` or `updated` (files which are added but not committed),
 384         `changed` (files which are changed but not added in the index),
 385         or `untracked` (files which are not tracked by git). The values of
 386         these variables may be specified as in color.branch.<slot>.
 387
 388 diff.renameLimit::
 389         The number of files to consider when performing the copy/rename
 390         detection; equivalent to the git diff option '-l'.
 391
 392 diff.renames::
 393         Tells git to detect renames.  If set to any boolean value, it
 394         will enable basic rename detection.  If set to "copies" or
 395         "copy", it will detect copies, as well.
 396
 397 fetch.unpackLimit::
 398         If the number of objects fetched over the git native
 399         transfer is below this
 400         limit, then the objects will be unpacked into loose object
 401         files. However if the number of received objects equals or
 402         exceeds this limit then the received pack will be stored as
 403         a pack, after adding any missing delta bases.  Storing the
 404         pack from a push can make the push operation complete faster,
 405         especially on slow filesystems.
 406
 407 format.headers::
 408         Additional email headers to include in a patch to be submitted
 409         by mail.  See gitlink:git-format-patch[1].
 410
 411 format.suffix::
 412         The default for format-patch is to output files with the suffix
 413         `.patch`. Use this variable to change that suffix (make sure to
 414         include the dot if you want it).
 415
 416 gc.aggressiveWindow::
 417         The window size parameter used in the delta compression
 418         algorithm used by 'git gc --aggressive'.  This defaults
 419         to 10.
 420
 421 gc.packrefs::
 422         `git gc` does not run `git pack-refs` in a bare repository by
 423         default so that older dumb-transport clients can still fetch
 424         from the repository.  Setting this to `true` lets `git
 425         gc` to run `git pack-refs`.  Setting this to `false` tells
 426         `git gc` never to run `git pack-refs`. The default setting is
 427         `notbare`. Enable it only when you know you do not have to
 428         support such clients.  The default setting will change to `true`
 429         at some stage, and setting this to `false` will continue to
 430         prevent `git pack-refs` from being run from `git gc`.
 431
 432 gc.reflogexpire::
 433         `git reflog expire` removes reflog entries older than
 434         this time; defaults to 90 days.
 435
 436 gc.reflogexpireunreachable::
 437         `git reflog expire` removes reflog entries older than
 438         this time and are not reachable from the current tip;
 439         defaults to 30 days.
 440
 441 gc.rerereresolved::
 442         Records of conflicted merge you resolved earlier are
 443         kept for this many days when `git rerere gc` is run.
 444         The default is 60 days.  See gitlink:git-rerere[1].
 445
 446 gc.rerereunresolved::
 447         Records of conflicted merge you have not resolved are
 448         kept for this many days when `git rerere gc` is run.
 449         The default is 15 days.  See gitlink:git-rerere[1].
 450
 451 rerere.enabled::
 452         Activate recording of resolved conflicts, so that identical
 453         conflict hunks can be resolved automatically, should they
 454         be encountered again.  See gitlink:git-rerere[1].
 455
 456 gitcvs.enabled::
 457         Whether the cvs server interface is enabled for this repository.
 458         See gitlink:git-cvsserver[1].
 459
 460 gitcvs.logfile::
 461         Path to a log file where the cvs server interface well... logs
 462         various stuff. See gitlink:git-cvsserver[1].
 463
 464 gitcvs.allbinary::
 465         If true, all files are sent to the client in mode '-kb'. This
 466         causes the client to treat all files as binary files which suppresses
 467         any newline munging it otherwise might do. A work-around for the
 468         fact that there is no way yet to set single files to mode '-kb'.
 469
 470 gitcvs.dbname::
 471         Database used by git-cvsserver to cache revision information
 472         derived from the git repository. The exact meaning depends on the
 473         used database driver, for SQLite (which is the default driver) this
 474         is a filename. Supports variable substitution (see
 475         gitlink:git-cvsserver[1] for details). May not contain semicolons (`;`).
 476         Default: '%Ggitcvs.%m.sqlite'
 477
 478 gitcvs.dbdriver::
 479         Used Perl DBI driver. You can specify any available driver
 480         for this here, but it might not work. git-cvsserver is tested
 481         with 'DBD::SQLite', reported to work with 'DBD::Pg', and
 482         reported *not* to work with 'DBD::mysql'. Experimental feature.
 483         May not contain double colons (`:`). Default: 'SQLite'.
 484         See gitlink:git-cvsserver[1].
 485
 486 gitcvs.dbuser, gitcvs.dbpass::
 487         Database user and password. Only useful if setting 'gitcvs.dbdriver',
 488         since SQLite has no concept of database users and/or passwords.
 489         'gitcvs.dbuser' supports variable substitution (see
 490         gitlink:git-cvsserver[1] for details).
 491
 492 All gitcvs variables except for 'gitcvs.allbinary' can also specifed
 493 as 'gitcvs.<access_method>.<varname>' (where 'access_method' is one
 494 of "ext" and "pserver") to make them apply only for the given access
 495 method.
 496
 497 http.sslVerify::
 498         Whether to verify the SSL certificate when fetching or pushing
 499         over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
 500         variable.
 501
 502 http.sslCert::
 503         File containing the SSL certificate when fetching or pushing
 504         over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
 505         variable.
 506
 507 http.sslKey::
 508         File containing the SSL private key when fetching or pushing
 509         over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
 510         variable.
 511
 512 http.sslCAInfo::
 513         File containing the certificates to verify the peer with when
 514         fetching or pushing over HTTPS. Can be overridden by the
 515         'GIT_SSL_CAINFO' environment variable.
 516
 517 http.sslCAPath::
 518         Path containing files with the CA certificates to verify the peer
 519         with when fetching or pushing over HTTPS. Can be overridden
 520         by the 'GIT_SSL_CAPATH' environment variable.
 521
 522 http.maxRequests::
 523         How many HTTP requests to launch in parallel. Can be overridden
 524         by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
 525
 526 http.lowSpeedLimit, http.lowSpeedTime::
 527         If the HTTP transfer speed is less than 'http.lowSpeedLimit'
 528         for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
 529         Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
 530         'GIT_HTTP_LOW_SPEED_TIME' environment variables.
 531
 532 http.noEPSV::
 533         A boolean which disables using of EPSV ftp command by curl.
 534         This can helpful with some "poor" ftp servers which don't
 535         support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
 536         environment variable. Default is false (curl will use EPSV).
 537
 538 i18n.commitEncoding::
 539         Character encoding the commit messages are stored in; git itself
 540         does not care per se, but this information is necessary e.g. when
 541         importing commits from emails or in the gitk graphical history
 542         browser (and possibly at other places in the future or in other
 543         porcelains). See e.g. gitlink:git-mailinfo[1]. Defaults to 'utf-8'.
 544
 545 i18n.logOutputEncoding::
 546         Character encoding the commit messages are converted to when
 547         running `git-log` and friends.
 548
 549 log.showroot::
 550         If true, the initial commit will be shown as a big creation event.
 551         This is equivalent to a diff against an empty tree.
 552         Tools like gitlink:git-log[1] or gitlink:git-whatchanged[1], which
 553         normally hide the root commit will now show it. True by default.
 554
 555 merge.summary::
 556         Whether to include summaries of merged commits in newly created
 557         merge commit messages. False by default.
 558
 559 merge.tool::
 560         Controls which merge resolution program is used by
 561         gitlink:git-mergetool[l].  Valid values are: "kdiff3", "tkdiff",
 562         "meld", "xxdiff", "emerge", "vimdiff", "gvimdiff", and "opendiff".
 563
 564 merge.verbosity::
 565         Controls the amount of output shown by the recursive merge
 566         strategy.  Level 0 outputs nothing except a final error
 567         message if conflicts were detected. Level 1 outputs only
 568         conflicts, 2 outputs conflicts and file changes.  Level 5 and
 569         above outputs debugging information.  The default is level 2.
 570
 571 merge.<driver>.name::
 572         Defines a human readable name for a custom low-level
 573         merge driver.  See gitlink:gitattributes[5] for details.
 574
 575 merge.<driver>.driver::
 576         Defines the command that implements a custom low-level
 577         merge driver.  See gitlink:gitattributes[5] for details.
 578
 579 merge.<driver>.recursive::
 580         Names a low-level merge driver to be used when
 581         performing an internal merge between common ancestors.
 582         See gitlink:gitattributes[5] for details.
 583
 584 pack.window::
 585         The size of the window used by gitlink:git-pack-objects[1] when no
 586         window size is given on the command line. Defaults to 10.
 587
 588 pack.depth::
 589         The maximum delta depth used by gitlink:git-pack-objects[1] when no
 590         maximum depth is given on the command line. Defaults to 50.
 591
 592 pack.windowMemory::
 593         The window memory size limit used by gitlink:git-pack-objects[1]
 594         when no limit is given on the command line.  The value can be
 595         suffixed with "k", "m", or "g".  Defaults to 0, meaning no
 596         limit.
 597
 598 pack.compression::
 599         An integer -1..9, indicating the compression level for objects
 600         in a pack file. -1 is the zlib default. 0 means no
 601         compression, and 1..9 are various speed/size tradeoffs, 9 being
 602         slowest.  If not set,  defaults to core.compression.  If that is
 603         not set,  defaults to -1.
 604
 605 pack.deltaCacheSize::
 606         The maxium memory in bytes used for caching deltas in
 607         gitlink:git-pack-objects[1].
 608         A value of 0 means no limit. Defaults to 0.
 609
 610 pack.deltaCacheLimit::
 611         The maxium size of a delta, that is cached in
 612         gitlink:git-pack-objects[1]. Defaults to 1000.
 613
 614 pull.octopus::
 615         The default merge strategy to use when pulling multiple branches
 616         at once.
 617
 618 pull.twohead::
 619         The default merge strategy to use when pulling a single branch.
 620
 621 remote.<name>.url::
 622         The URL of a remote repository.  See gitlink:git-fetch[1] or
 623         gitlink:git-push[1].
 624
 625 remote.<name>.fetch::
 626         The default set of "refspec" for gitlink:git-fetch[1]. See
 627         gitlink:git-fetch[1].
 628
 629 remote.<name>.push::
 630         The default set of "refspec" for gitlink:git-push[1]. See
 631         gitlink:git-push[1].
 632
 633 remote.<name>.skipDefaultUpdate::
 634         If true, this remote will be skipped by default when updating
 635         using the remote subcommand of gitlink:git-remote[1].
 636
 637 remote.<name>.receivepack::
 638         The default program to execute on the remote side when pushing.  See
 639         option \--exec of gitlink:git-push[1].
 640
 641 remote.<name>.uploadpack::
 642         The default program to execute on the remote side when fetching.  See
 643         option \--exec of gitlink:git-fetch-pack[1].
 644
 645 remote.<name>.tagopt::
 646         Setting this value to --no-tags disables automatic tag following when fetching
 647         from remote <name>
 648
 649 remotes.<group>::
 650         The list of remotes which are fetched by "git remote update
 651         <group>".  See gitlink:git-remote[1].
 652
 653 repack.usedeltabaseoffset::
 654         Allow gitlink:git-repack[1] to create packs that uses
 655         delta-base offset.  Defaults to false.
 656
 657 show.difftree::
 658         The default gitlink:git-diff-tree[1] arguments to be used
 659         for gitlink:git-show[1].
 660
 661 showbranch.default::
 662         The default set of branches for gitlink:git-show-branch[1].
 663         See gitlink:git-show-branch[1].
 664
 665 tar.umask::
 666         By default, gitlink:git-tar-tree[1] sets file and directories modes
 667         to 0666 or 0777. While this is both useful and acceptable for projects
 668         such as the Linux Kernel, it might be excessive for other projects.
 669         With this variable, it becomes possible to tell
 670         gitlink:git-tar-tree[1] to apply a specific umask to the modes above.
 671         The special value "user" indicates that the user's current umask will
 672         be used. This should be enough for most projects, as it will lead to
 673         the same permissions as gitlink:git-checkout[1] would use. The default
 674         value remains 0, which means world read-write.
 675
 676 user.email::
 677         Your email address to be recorded in any newly created commits.
 678         Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
 679         'EMAIL' environment variables.  See gitlink:git-commit-tree[1].
 680
 681 user.name::
 682         Your full name to be recorded in any newly created commits.
 683         Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
 684         environment variables.  See gitlink:git-commit-tree[1].
 685
 686 user.signingkey::
 687         If gitlink:git-tag[1] is not selecting the key you want it to
 688         automatically when creating a signed tag, you can override the
 689         default selection with this variable.  This option is passed
 690         unchanged to gpg's --local-user parameter, so you may specify a key
 691         using any method that gpg supports.
 692
 693 whatchanged.difftree::
 694         The default gitlink:git-diff-tree[1] arguments to be used
 695         for gitlink:git-whatchanged[1].
 696
 697 imap::
 698         The configuration variables in the 'imap' section are described
 699         in gitlink:git-imap-send[1].
 700
 701 receive.unpackLimit::
 702         If the number of objects received in a push is below this
 703         limit then the objects will be unpacked into loose object
 704         files. However if the number of received objects equals or
 705         exceeds this limit then the received pack will be stored as
 706         a pack, after adding any missing delta bases.  Storing the
 707         pack from a push can make the push operation complete faster,
 708         especially on slow filesystems.
 709
 710 receive.denyNonFastForwards::
 711         If set to true, git-receive-pack will deny a ref update which is
 712         not a fast forward. Use this to prevent such an update via a push,
 713         even if that push is forced. This configuration variable is
 714         set when initializing a shared repository.
 715
 716 transfer.unpackLimit::
 717         When `fetch.unpackLimit` or `receive.unpackLimit` are
 718         not set, the value of this variable is used instead.