1CONFIGURATION FILE 2------------------ 3 4The git configuration file contains a number of variables that affect 5the git command's behavior. The `.git/config` file in each repository 6is used to store the configuration for that repository, and 7`$HOME/.gitconfig` is used to store a per-user configuration as 8fallback values for the `.git/config` file. The file `/etc/gitconfig` 9can be used to store a system-wide default configuration. 10 11The configuration variables are used by both the git plumbing 12and the porcelains. The variables are divided into sections, wherein 13the fully qualified variable name of the variable itself is the last 14dot-separated segment and the section name is everything before the last 15dot. The variable names are case-insensitive and only alphanumeric 16characters are allowed. Some variables may appear multiple times. 17 18Syntax 19~~~~~~ 20 21The syntax is fairly flexible and permissive; whitespaces are mostly 22ignored. The '#' and ';' characters begin comments to the end of line, 23blank lines are ignored. 24 25The file consists of sections and variables. A section begins with 26the name of the section in square brackets and continues until the next 27section begins. Section names are not case sensitive. Only alphanumeric 28characters, `-` and `.` are allowed in section names. Each variable 29must belong to some section, which means that there must be a section 30header before the first setting of a variable. 31 32Sections can be further divided into subsections. To begin a subsection 33put its name in double quotes, separated by space from the section name, 34in the section header, like in the example below: 35 36-------- 37 [section "subsection"] 38 39-------- 40 41Subsection names are case sensitive and can contain any characters except 42newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`, 43respectively). Section headers cannot span multiple 44lines. Variables may belong directly to a section or to a given subsection. 45You can have `[section]` if you have `[section "subsection"]`, but you 46don't need to. 47 48There is also a case insensitive alternative `[section.subsection]` syntax. 49In this syntax, subsection names follow the same restrictions as for section 50names. 51 52All 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 54is taken as 'name' and the variable is recognized as boolean "true". 55The variable names are case-insensitive and only alphanumeric 56characters and `-` are allowed. There can be more than one value 57for a given variable; we say then that variable is multivalued. 58 59Leading and trailing whitespace in a variable value is discarded. 60Internal whitespace within a variable value is retained verbatim. 61 62The values following the equals sign in variable assign are all either 63a string, an integer, or a boolean. Boolean values may be given as yes/no, 640/1, true/false or on/off. Case is not significant in boolean values, when 65converting value to the canonical form using '--bool' type specifier; 66'git-config' will ensure that the output is "true" or "false". 67 68String values may be entirely or partially enclosed in double quotes. 69You need to enclose variable values in double quotes if you want to 70preserve leading or trailing whitespace, or if the variable value contains 71comment characters (i.e. it contains '#' or ';'). 72Double quote `"` and backslash `\` characters in variable values must 73be escaped: use `\"` for `"` and `\\` for `\`. 74 75The following escape sequences (beside `\"` and `\\`) are recognized: 76`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) 77and `\b` for backspace (BS). No other char escape sequence, nor octal 78char sequences are valid. 79 80Variable values ending in a `\` are continued on the next line in the 81customary UNIX fashion. 82 83Some variables may require a special value format. 84 85Example 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/diff-wrapper 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 "kernel.org" 105 gitProxy=default-proxy ; for the rest 106 107Variables 108~~~~~~~~~ 109 110Note that this list is non-comprehensive and not necessarily complete. 111For command-specific variables, you will find a more detailed description 112in the appropriate manual page. You will find a description of non-core 113porcelain configuration variables in the respective porcelain documentation. 114 115core.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 linkgit:git-update-index[1]. True by default. 119 120core.ignoreCygwinFSTricks:: 121 This option is only used by Cygwin implementation of Git. If false, 122 the Cygwin stat() and lstat() functions are used. This may be useful 123 if your repository consists of a few separate directories joined in 124 one hierarchy using Cygwin mount. If true, Git uses native Win32 API 125 whenever it is possible and falls back to Cygwin functions only to 126 handle symbol links. The native mode is more than twice faster than 127 normal Cygwin l/stat() functions. True by default, unless core.filemode 128 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's 129 POSIX emulation is required to support core.filemode. 130 131core.trustctime:: 132 If false, the ctime differences between the index and the 133 working copy are ignored; useful when the inode change time 134 is regularly modified by something outside Git (file system 135 crawlers and some backup systems). 136 See linkgit:git-update-index[1]. True by default. 137 138core.quotepath:: 139 The commands that output paths (e.g. 'ls-files', 140 'diff'), when not given the `-z` option, will quote 141 "unusual" characters in the pathname by enclosing the 142 pathname in a double-quote pair and with backslashes the 143 same way strings in C source code are quoted. If this 144 variable is set to false, the bytes higher than 0x80 are 145 not quoted but output as verbatim. Note that double 146 quote, backslash and control characters are always 147 quoted without `-z` regardless of the setting of this 148 variable. 149 150core.autocrlf:: 151 If true, makes git convert `CRLF` at the end of lines in text files to 152 `LF` when reading from the filesystem, and convert in reverse when 153 writing to the filesystem. The variable can be set to 154 'input', in which case the conversion happens only while 155 reading from the filesystem but files are written out with 156 `LF` at the end of lines. Currently, which paths to consider 157 "text" (i.e. be subjected to the autocrlf mechanism) is 158 decided purely based on the contents. 159 160core.safecrlf:: 161 If true, makes git check if converting `CRLF` as controlled by 162 `core.autocrlf` is reversible. Git will verify if a command 163 modifies a file in the work tree either directly or indirectly. 164 For example, committing a file followed by checking out the 165 same file should yield the original file in the work tree. If 166 this is not the case for the current setting of 167 `core.autocrlf`, git will reject the file. The variable can 168 be set to "warn", in which case git will only warn about an 169 irreversible conversion but continue the operation. 170+ 171CRLF conversion bears a slight chance of corrupting data. 172autocrlf=true will convert CRLF to LF during commit and LF to 173CRLF during checkout. A file that contains a mixture of LF and 174CRLF before the commit cannot be recreated by git. For text 175files this is the right thing to do: it corrects line endings 176such that we have only LF line endings in the repository. 177But for binary files that are accidentally classified as text the 178conversion can corrupt data. 179+ 180If you recognize such corruption early you can easily fix it by 181setting the conversion type explicitly in .gitattributes. Right 182after committing you still have the original file in your work 183tree and this file is not yet corrupted. You can explicitly tell 184git that this file is binary and git will handle the file 185appropriately. 186+ 187Unfortunately, the desired effect of cleaning up text files with 188mixed line endings and the undesired effect of corrupting binary 189files cannot be distinguished. In both cases CRLFs are removed 190in an irreversible way. For text files this is the right thing 191to do because CRLFs are line endings, while for binary files 192converting CRLFs corrupts data. 193+ 194Note, this safety check does not mean that a checkout will generate a 195file identical to the original file for a different setting of 196`core.autocrlf`, but only for the current one. For example, a text 197file with `LF` would be accepted with `core.autocrlf=input` and could 198later be checked out with `core.autocrlf=true`, in which case the 199resulting file would contain `CRLF`, although the original file 200contained `LF`. However, in both work trees the line endings would be 201consistent, that is either all `LF` or all `CRLF`, but never mixed. A 202file with mixed line endings would be reported by the `core.safecrlf` 203mechanism. 204 205core.symlinks:: 206 If false, symbolic links are checked out as small plain files that 207 contain the link text. linkgit:git-update-index[1] and 208 linkgit:git-add[1] will not change the recorded type to regular 209 file. Useful on filesystems like FAT that do not support 210 symbolic links. True by default. 211 212core.gitProxy:: 213 A "proxy command" to execute (as 'command host port') instead 214 of establishing direct connection to the remote server when 215 using the git protocol for fetching. If the variable value is 216 in the "COMMAND for DOMAIN" format, the command is applied only 217 on hostnames ending with the specified domain string. This variable 218 may be set multiple times and is matched in the given order; 219 the first match wins. 220+ 221Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 222(which always applies universally, without the special "for" 223handling). 224+ 225The special string `none` can be used as the proxy command to 226specify that no proxy be used for a given domain pattern. 227This is useful for excluding servers inside a firewall from 228proxy use, while defaulting to a common proxy for external domains. 229 230core.ignoreStat:: 231 If true, commands which modify both the working tree and the index 232 will mark the updated paths with the "assume unchanged" bit in the 233 index. These marked files are then assumed to stay unchanged in the 234 working copy, until you mark them otherwise manually - Git will not 235 detect the file changes by lstat() calls. This is useful on systems 236 where those are very slow, such as Microsoft Windows. 237 See linkgit:git-update-index[1]. 238 False by default. 239 240core.preferSymlinkRefs:: 241 Instead of the default "symref" format for HEAD 242 and other symbolic reference files, use symbolic links. 243 This is sometimes needed to work with old scripts that 244 expect HEAD to be a symbolic link. 245 246core.bare:: 247 If true this repository is assumed to be 'bare' and has no 248 working directory associated with it. If this is the case a 249 number of commands that require a working directory will be 250 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 251+ 252This setting is automatically guessed by linkgit:git-clone[1] or 253linkgit:git-init[1] when the repository was created. By default a 254repository that ends in "/.git" is assumed to be not bare (bare = 255false), while all other repositories are assumed to be bare (bare 256= true). 257 258core.worktree:: 259 Set the path to the working tree. The value will not be 260 used in combination with repositories found automatically in 261 a .git directory (i.e. $GIT_DIR is not set). 262 This can be overridden by the GIT_WORK_TREE environment 263 variable and the '--work-tree' command line option. It can be 264 a absolute path or relative path to the directory specified by 265 --git-dir or GIT_DIR. 266 Note: If --git-dir or GIT_DIR are specified but none of 267 --work-tree, GIT_WORK_TREE and core.worktree is specified, 268 the current working directory is regarded as the top directory 269 of your working tree. 270 271core.logAllRefUpdates:: 272 Enable the reflog. Updates to a ref <ref> is logged to the file 273 "$GIT_DIR/logs/<ref>", by appending the new and old 274 SHA1, the date/time and the reason of the update, but 275 only when the file exists. If this configuration 276 variable is set to true, missing "$GIT_DIR/logs/<ref>" 277 file is automatically created for branch heads. 278+ 279This information can be used to determine what commit 280was the tip of a branch "2 days ago". 281+ 282This value is true by default in a repository that has 283a working directory associated with it, and false by 284default in a bare repository. 285 286core.repositoryFormatVersion:: 287 Internal variable identifying the repository format and layout 288 version. 289 290core.sharedRepository:: 291 When 'group' (or 'true'), the repository is made shareable between 292 several users in a group (making sure all the files and objects are 293 group-writable). When 'all' (or 'world' or 'everybody'), the 294 repository will be readable by all users, additionally to being 295 group-shareable. When 'umask' (or 'false'), git will use permissions 296 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 297 files in the repository will have this mode value. '0xxx' will override 298 user's umask value (whereas the other options will only override 299 requested parts of the user's umask value). Examples: '0660' will make 300 the repo read/write-able for the owner and group, but inaccessible to 301 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 302 repository that is group-readable but not group-writable. 303 See linkgit:git-init[1]. False by default. 304 305core.warnAmbiguousRefs:: 306 If true, git will warn you if the ref name you passed it is ambiguous 307 and might match multiple refs in the .git/refs/ tree. True by default. 308 309core.compression:: 310 An integer -1..9, indicating a default compression level. 311 -1 is the zlib default. 0 means no compression, 312 and 1..9 are various speed/size tradeoffs, 9 being slowest. 313 If set, this provides a default to other compression variables, 314 such as 'core.loosecompression' and 'pack.compression'. 315 316core.loosecompression:: 317 An integer -1..9, indicating the compression level for objects that 318 are not in a pack file. -1 is the zlib default. 0 means no 319 compression, and 1..9 are various speed/size tradeoffs, 9 being 320 slowest. If not set, defaults to core.compression. If that is 321 not set, defaults to 1 (best speed). 322 323core.packedGitWindowSize:: 324 Number of bytes of a pack file to map into memory in a 325 single mapping operation. Larger window sizes may allow 326 your system to process a smaller number of large pack files 327 more quickly. Smaller window sizes will negatively affect 328 performance due to increased calls to the operating system's 329 memory manager, but may improve performance when accessing 330 a large number of large pack files. 331+ 332Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 333MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 334be reasonable for all users/operating systems. You probably do 335not need to adjust this value. 336+ 337Common unit suffixes of 'k', 'm', or 'g' are supported. 338 339core.packedGitLimit:: 340 Maximum number of bytes to map simultaneously into memory 341 from pack files. If Git needs to access more than this many 342 bytes at once to complete an operation it will unmap existing 343 regions to reclaim virtual address space within the process. 344+ 345Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 346This should be reasonable for all users/operating systems, except on 347the largest projects. You probably do not need to adjust this value. 348+ 349Common unit suffixes of 'k', 'm', or 'g' are supported. 350 351core.deltaBaseCacheLimit:: 352 Maximum number of bytes to reserve for caching base objects 353 that multiple deltafied objects reference. By storing the 354 entire decompressed base objects in a cache Git is able 355 to avoid unpacking and decompressing frequently used base 356 objects multiple times. 357+ 358Default is 16 MiB on all platforms. This should be reasonable 359for all users/operating systems, except on the largest projects. 360You probably do not need to adjust this value. 361+ 362Common unit suffixes of 'k', 'm', or 'g' are supported. 363 364core.excludesfile:: 365 In addition to '.gitignore' (per-directory) and 366 '.git/info/exclude', git looks into this file for patterns 367 of files which are not meant to be tracked. See 368 linkgit:gitignore[5]. 369 370core.editor:: 371 Commands such as `commit` and `tag` that lets you edit 372 messages by launching an editor uses the value of this 373 variable when it is set, and the environment variable 374 `GIT_EDITOR` is not set. The order of preference is 375 `GIT_EDITOR` environment, `core.editor`, `VISUAL` and 376 `EDITOR` environment variables and then finally `vi`. 377 378core.pager:: 379 The command that git will use to paginate output. Can 380 be overridden with the `GIT_PAGER` environment 381 variable. Note that git sets the `LESS` environment 382 variable to `FRSX` if it is unset when it runs the 383 pager. One can change these settings by setting the 384 `LESS` variable to some other value. Alternately, 385 these settings can be overridden on a project or 386 global basis by setting the `core.pager` option. 387 Setting `core.pager` has no affect on the `LESS` 388 environment variable behaviour above, so if you want 389 to override git's default settings this way, you need 390 to be explicit. For example, to disable the S option 391 in a backward compatible manner, set `core.pager` 392 to `less -+$LESS -FRX`. This will be passed to the 393 shell by git, which will translate the final command to 394 `LESS=FRSX less -+FRSX -FRX`. 395 396core.whitespace:: 397 A comma separated list of common whitespace problems to 398 notice. 'git-diff' will use `color.diff.whitespace` to 399 highlight them, and 'git-apply --whitespace=error' will 400 consider them as errors. You can prefix `-` to disable 401 any of them (e.g. `-trailing-space`): 402+ 403* `trailing-space` treats trailing whitespaces at the end of the line 404 as an error (enabled by default). 405* `space-before-tab` treats a space character that appears immediately 406 before a tab character in the initial indent part of the line as an 407 error (enabled by default). 408* `indent-with-non-tab` treats a line that is indented with 8 or more 409 space characters as an error (not enabled by default). 410* `cr-at-eol` treats a carriage-return at the end of line as 411 part of the line terminator, i.e. with it, `trailing-space` 412 does not trigger if the character before such a carriage-return 413 is not a whitespace (not enabled by default). 414 415core.fsyncobjectfiles:: 416 This boolean will enable 'fsync()' when writing object files. 417+ 418This is a total waste of time and effort on a filesystem that orders 419data writes properly, but can be useful for filesystems that do not use 420journalling (traditional UNIX filesystems) or that only journal metadata 421and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 422 423core.preloadindex:: 424 Enable parallel index preload for operations like 'git diff' 425+ 426This can speed up operations like 'git diff' and 'git status' especially 427on filesystems like NFS that have weak caching semantics and thus 428relatively high IO latencies. With this set to 'true', git will do the 429index comparison to the filesystem data in parallel, allowing 430overlapping IO's. 431 432core.createObject:: 433 You can set this to 'link', in which case a hardlink followed by 434 a delete of the source are used to make sure that object creation 435 will not overwrite existing objects. 436+ 437On some file system/operating system combinations, this is unreliable. 438Set this config setting to 'rename' there; However, This will remove the 439check that makes sure that existing object files will not get overwritten. 440 441add.ignore-errors:: 442 Tells 'git-add' to continue adding files when some files cannot be 443 added due to indexing errors. Equivalent to the '--ignore-errors' 444 option of linkgit:git-add[1]. 445 446alias.*:: 447 Command aliases for the linkgit:git[1] command wrapper - e.g. 448 after defining "alias.last = cat-file commit HEAD", the invocation 449 "git last" is equivalent to "git cat-file commit HEAD". To avoid 450 confusion and troubles with script usage, aliases that 451 hide existing git commands are ignored. Arguments are split by 452 spaces, the usual shell quoting and escaping is supported. 453 quote pair and a backslash can be used to quote them. 454+ 455If the alias expansion is prefixed with an exclamation point, 456it will be treated as a shell command. For example, defining 457"alias.new = !gitk --all --not ORIG_HEAD", the invocation 458"git new" is equivalent to running the shell command 459"gitk --all --not ORIG_HEAD". Note that shell commands will be 460executed from the top-level directory of a repository, which may 461not necessarily be the current directory. 462 463apply.whitespace:: 464 Tells 'git-apply' how to handle whitespaces, in the same way 465 as the '--whitespace' option. See linkgit:git-apply[1]. 466 467branch.autosetupmerge:: 468 Tells 'git-branch' and 'git-checkout' to setup new branches 469 so that linkgit:git-pull[1] will appropriately merge from the 470 starting point branch. Note that even if this option is not set, 471 this behavior can be chosen per-branch using the `--track` 472 and `--no-track` options. The valid settings are: `false` -- no 473 automatic setup is done; `true` -- automatic setup is done when the 474 starting point is a remote branch; `always` -- automatic setup is 475 done when the starting point is either a local branch or remote 476 branch. This option defaults to true. 477 478branch.autosetuprebase:: 479 When a new branch is created with 'git-branch' or 'git-checkout' 480 that tracks another branch, this variable tells git to set 481 up pull to rebase instead of merge (see "branch.<name>.rebase"). 482 When `never`, rebase is never automatically set to true. 483 When `local`, rebase is set to true for tracked branches of 484 other local branches. 485 When `remote`, rebase is set to true for tracked branches of 486 remote branches. 487 When `always`, rebase will be set to true for all tracking 488 branches. 489 See "branch.autosetupmerge" for details on how to set up a 490 branch to track another branch. 491 This option defaults to never. 492 493branch.<name>.remote:: 494 When in branch <name>, it tells 'git-fetch' and 'git-push' which 495 remote to fetch from/push to. It defaults to `origin` if no remote is 496 configured. `origin` is also used if you are not on any branch. 497 498branch.<name>.merge:: 499 Defines, together with branch.<name>.remote, the upstream branch 500 for the given branch. It tells 'git-fetch'/'git-pull' which 501 branch to merge and can also affect 'git-push' (see push.default). 502 When in branch <name>, it tells 'git-fetch' the default 503 refspec to be marked for merging in FETCH_HEAD. The value is 504 handled like the remote part of a refspec, and must match a 505 ref which is fetched from the remote given by 506 "branch.<name>.remote". 507 The merge information is used by 'git-pull' (which at first calls 508 'git-fetch') to lookup the default branch for merging. Without 509 this option, 'git-pull' defaults to merge the first refspec fetched. 510 Specify multiple values to get an octopus merge. 511 If you wish to setup 'git-pull' so that it merges into <name> from 512 another branch in the local repository, you can point 513 branch.<name>.merge to the desired branch, and use the special setting 514 `.` (a period) for branch.<name>.remote. 515 516branch.<name>.mergeoptions:: 517 Sets default options for merging into branch <name>. The syntax and 518 supported options are equal to that of linkgit:git-merge[1], but 519 option values containing whitespace characters are currently not 520 supported. 521 522branch.<name>.rebase:: 523 When true, rebase the branch <name> on top of the fetched branch, 524 instead of merging the default branch from the default remote when 525 "git pull" is run. 526 *NOTE*: this is a possibly dangerous operation; do *not* use 527 it unless you understand the implications (see linkgit:git-rebase[1] 528 for details). 529 530browser.<tool>.cmd:: 531 Specify the command to invoke the specified browser. The 532 specified command is evaluated in shell with the URLs passed 533 as arguments. (See linkgit:git-web--browse[1].) 534 535browser.<tool>.path:: 536 Override the path for the given tool that may be used to 537 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 538 working repository in gitweb (see linkgit:git-instaweb[1]). 539 540clean.requireForce:: 541 A boolean to make git-clean do nothing unless given -f 542 or -n. Defaults to true. 543 544color.branch:: 545 A boolean to enable/disable color in the output of 546 linkgit:git-branch[1]. May be set to `always`, 547 `false` (or `never`) or `auto` (or `true`), in which case colors are used 548 only when the output is to a terminal. Defaults to false. 549 550color.branch.<slot>:: 551 Use customized color for branch coloration. `<slot>` is one of 552 `current` (the current branch), `local` (a local branch), 553 `remote` (a tracking branch in refs/remotes/), `plain` (other 554 refs). 555+ 556The value for these configuration variables is a list of colors (at most 557two) and attributes (at most one), separated by spaces. The colors 558accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`, 559`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`, 560`blink` and `reverse`. The first color given is the foreground; the 561second is the background. The position of the attribute, if any, 562doesn't matter. 563 564color.diff:: 565 When set to `always`, always use colors in patch. 566 When false (or `never`), never. When set to `true` or `auto`, use 567 colors only when the output is to the terminal. Defaults to false. 568 569color.diff.<slot>:: 570 Use customized color for diff colorization. `<slot>` specifies 571 which part of the patch to use the specified color, and is one 572 of `plain` (context text), `meta` (metainformation), `frag` 573 (hunk header), `old` (removed lines), `new` (added lines), 574 `commit` (commit headers), or `whitespace` (highlighting 575 whitespace errors). The values of these variables may be specified as 576 in color.branch.<slot>. 577 578color.grep:: 579 When set to `always`, always highlight matches. When `false` (or 580 `never`), never. When set to `true` or `auto`, use color only 581 when the output is written to the terminal. Defaults to `false`. 582 583color.grep.external:: 584 The string value of this variable is passed to an external 'grep' 585 command as a command line option if match highlighting is turned 586 on. If set to an empty string, no option is passed at all, 587 turning off coloring for external 'grep' calls; this is the default. 588 For GNU grep, set it to `--color=always` to highlight matches even 589 when a pager is used. 590 591color.grep.match:: 592 Use customized color for matches. The value of this variable 593 may be specified as in color.branch.<slot>. It is passed using 594 the environment variables 'GREP_COLOR' and 'GREP_COLORS' when 595 calling an external 'grep'. 596 597color.interactive:: 598 When set to `always`, always use colors for interactive prompts 599 and displays (such as those used by "git-add --interactive"). 600 When false (or `never`), never. When set to `true` or `auto`, use 601 colors only when the output is to the terminal. Defaults to false. 602 603color.interactive.<slot>:: 604 Use customized color for 'git-add --interactive' 605 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for 606 four distinct types of normal output from interactive 607 programs. The values of these variables may be specified as 608 in color.branch.<slot>. 609 610color.pager:: 611 A boolean to enable/disable colored output when the pager is in 612 use (default is true). 613 614color.showbranch:: 615 A boolean to enable/disable color in the output of 616 linkgit:git-show-branch[1]. May be set to `always`, 617 `false` (or `never`) or `auto` (or `true`), in which case colors are used 618 only when the output is to a terminal. Defaults to false. 619 620color.status:: 621 A boolean to enable/disable color in the output of 622 linkgit:git-status[1]. May be set to `always`, 623 `false` (or `never`) or `auto` (or `true`), in which case colors are used 624 only when the output is to a terminal. Defaults to false. 625 626color.status.<slot>:: 627 Use customized color for status colorization. `<slot>` is 628 one of `header` (the header text of the status message), 629 `added` or `updated` (files which are added but not committed), 630 `changed` (files which are changed but not added in the index), 631 `untracked` (files which are not tracked by git), or 632 `nobranch` (the color the 'no branch' warning is shown in, defaulting 633 to red). The values of these variables may be specified as in 634 color.branch.<slot>. 635 636color.ui:: 637 When set to `always`, always use colors in all git commands which 638 are capable of colored output. When false (or `never`), never. When 639 set to `true` or `auto`, use colors only when the output is to the 640 terminal. When more specific variables of color.* are set, they always 641 take precedence over this setting. Defaults to false. 642 643commit.template:: 644 Specify a file to use as the template for new commit messages. 645 646diff.autorefreshindex:: 647 When using 'git-diff' to compare with work tree 648 files, do not consider stat-only change as changed. 649 Instead, silently run `git update-index --refresh` to 650 update the cached stat information for paths whose 651 contents in the work tree match the contents in the 652 index. This option defaults to true. Note that this 653 affects only 'git-diff' Porcelain, and not lower level 654 'diff' commands, such as 'git-diff-files'. 655 656diff.external:: 657 If this config variable is set, diff generation is not 658 performed using the internal diff machinery, but using the 659 given command. Can be overridden with the `GIT_EXTERNAL_DIFF' 660 environment variable. The command is called with parameters 661 as described under "git Diffs" in linkgit:git[1]. Note: if 662 you want to use an external diff program only on a subset of 663 your files, you might want to use linkgit:gitattributes[5] instead. 664 665diff.mnemonicprefix:: 666 If set, 'git-diff' uses a prefix pair that is different from the 667 standard "a/" and "b/" depending on what is being compared. When 668 this configuration is in effect, reverse diff output also swaps 669 the order of the prefixes: 670'git-diff';; 671 compares the (i)ndex and the (w)ork tree; 672'git-diff HEAD';; 673 compares a (c)ommit and the (w)ork tree; 674'git diff --cached';; 675 compares a (c)ommit and the (i)ndex; 676'git-diff HEAD:file1 file2';; 677 compares an (o)bject and a (w)ork tree entity; 678'git diff --no-index a b';; 679 compares two non-git things (1) and (2). 680 681diff.renameLimit:: 682 The number of files to consider when performing the copy/rename 683 detection; equivalent to the 'git-diff' option '-l'. 684 685diff.renames:: 686 Tells git to detect renames. If set to any boolean value, it 687 will enable basic rename detection. If set to "copies" or 688 "copy", it will detect copies, as well. 689 690diff.suppressBlankEmpty:: 691 A boolean to inhibit the standard behavior of printing a space 692 before each empty output line. Defaults to false. 693 694diff.tool:: 695 Controls which diff tool is used. `diff.tool` overrides 696 `merge.tool` when used by linkgit:git-difftool[1] and has 697 the same valid values as `merge.tool` minus "tortoisemerge" 698 and plus "kompare". 699 700difftool.<tool>.path:: 701 Override the path for the given tool. This is useful in case 702 your tool is not in the PATH. 703 704difftool.<tool>.cmd:: 705 Specify the command to invoke the specified diff tool. 706 The specified command is evaluated in shell with the following 707 variables available: 'LOCAL' is set to the name of the temporary 708 file containing the contents of the diff pre-image and 'REMOTE' 709 is set to the name of the temporary file containing the contents 710 of the diff post-image. 711 712difftool.prompt:: 713 Prompt before each invocation of the diff tool. 714 715diff.wordRegex:: 716 A POSIX Extended Regular Expression used to determine what is a "word" 717 when performing word-by-word difference calculations. Character 718 sequences that match the regular expression are "words", all other 719 characters are *ignorable* whitespace. 720 721fetch.unpackLimit:: 722 If the number of objects fetched over the git native 723 transfer is below this 724 limit, then the objects will be unpacked into loose object 725 files. However if the number of received objects equals or 726 exceeds this limit then the received pack will be stored as 727 a pack, after adding any missing delta bases. Storing the 728 pack from a push can make the push operation complete faster, 729 especially on slow filesystems. If not set, the value of 730 `transfer.unpackLimit` is used instead. 731 732format.attach:: 733 Enable multipart/mixed attachments as the default for 734 'format-patch'. The value can also be a double quoted string 735 which will enable attachments as the default and set the 736 value as the boundary. See the --attach option in 737 linkgit:git-format-patch[1]. 738 739format.numbered:: 740 A boolean which can enable or disable sequence numbers in patch 741 subjects. It defaults to "auto" which enables it only if there 742 is more than one patch. It can be enabled or disabled for all 743 messages by setting it to "true" or "false". See --numbered 744 option in linkgit:git-format-patch[1]. 745 746format.headers:: 747 Additional email headers to include in a patch to be submitted 748 by mail. See linkgit:git-format-patch[1]. 749 750format.cc:: 751 Additional "Cc:" headers to include in a patch to be submitted 752 by mail. See the --cc option in linkgit:git-format-patch[1]. 753 754format.subjectprefix:: 755 The default for format-patch is to output files with the '[PATCH]' 756 subject prefix. Use this variable to change that prefix. 757 758format.suffix:: 759 The default for format-patch is to output files with the suffix 760 `.patch`. Use this variable to change that suffix (make sure to 761 include the dot if you want it). 762 763format.pretty:: 764 The default pretty format for log/show/whatchanged command, 765 See linkgit:git-log[1], linkgit:git-show[1], 766 linkgit:git-whatchanged[1]. 767 768format.thread:: 769 The default threading style for 'git-format-patch'. Can be 770 either a boolean value, `shallow` or `deep`. `shallow` 771 threading makes every mail a reply to the head of the series, 772 where the head is chosen from the cover letter, the 773 `\--in-reply-to`, and the first patch mail, in this order. 774 `deep` threading makes every mail a reply to the previous one. 775 A true boolean value is the same as `shallow`, and a false 776 value disables threading. 777 778format.signoff:: 779 A boolean value which lets you enable the `-s/--signoff` option of 780 format-patch by default. *Note:* Adding the Signed-off-by: line to a 781 patch should be a conscious act and means that you certify you have 782 the rights to submit this work under the same open source license. 783 Please see the 'SubmittingPatches' document for further discussion. 784 785gc.aggressiveWindow:: 786 The window size parameter used in the delta compression 787 algorithm used by 'git-gc --aggressive'. This defaults 788 to 10. 789 790gc.auto:: 791 When there are approximately more than this many loose 792 objects in the repository, `git gc --auto` will pack them. 793 Some Porcelain commands use this command to perform a 794 light-weight garbage collection from time to time. The 795 default value is 6700. Setting this to 0 disables it. 796 797gc.autopacklimit:: 798 When there are more than this many packs that are not 799 marked with `*.keep` file in the repository, `git gc 800 --auto` consolidates them into one larger pack. The 801 default value is 50. Setting this to 0 disables it. 802 803gc.packrefs:: 804 'git-gc' does not run `git pack-refs` in a bare repository by 805 default so that older dumb-transport clients can still fetch 806 from the repository. Setting this to `true` lets 'git-gc' 807 to run `git pack-refs`. Setting this to `false` tells 808 'git-gc' never to run `git pack-refs`. The default setting is 809 `notbare`. Enable it only when you know you do not have to 810 support such clients. The default setting will change to `true` 811 at some stage, and setting this to `false` will continue to 812 prevent `git pack-refs` from being run from 'git-gc'. 813 814gc.pruneexpire:: 815 When 'git-gc' is run, it will call 'prune --expire 2.weeks.ago'. 816 Override the grace period with this config variable. The value 817 "now" may be used to disable this grace period and always prune 818 unreachable objects immediately. 819 820gc.reflogexpire:: 821 'git-reflog expire' removes reflog entries older than 822 this time; defaults to 90 days. 823 824gc.reflogexpireunreachable:: 825 'git-reflog expire' removes reflog entries older than 826 this time and are not reachable from the current tip; 827 defaults to 30 days. 828 829gc.rerereresolved:: 830 Records of conflicted merge you resolved earlier are 831 kept for this many days when 'git-rerere gc' is run. 832 The default is 60 days. See linkgit:git-rerere[1]. 833 834gc.rerereunresolved:: 835 Records of conflicted merge you have not resolved are 836 kept for this many days when 'git-rerere gc' is run. 837 The default is 15 days. See linkgit:git-rerere[1]. 838 839gitcvs.commitmsgannotation:: 840 Append this string to each commit message. Set to empty string 841 to disable this feature. Defaults to "via git-CVS emulator". 842 843gitcvs.enabled:: 844 Whether the CVS server interface is enabled for this repository. 845 See linkgit:git-cvsserver[1]. 846 847gitcvs.logfile:: 848 Path to a log file where the CVS server interface well... logs 849 various stuff. See linkgit:git-cvsserver[1]. 850 851gitcvs.usecrlfattr:: 852 If true, the server will look up the `crlf` attribute for 853 files to determine the '-k' modes to use. If `crlf` is set, 854 the '-k' mode will be left blank, so cvs clients will 855 treat it as text. If `crlf` is explicitly unset, the file 856 will be set with '-kb' mode, which suppresses any newline munging 857 the client might otherwise do. If `crlf` is not specified, 858 then 'gitcvs.allbinary' is used. See linkgit:gitattributes[5]. 859 860gitcvs.allbinary:: 861 This is used if 'gitcvs.usecrlfattr' does not resolve 862 the correct '-kb' mode to use. If true, all 863 unresolved files are sent to the client in 864 mode '-kb'. This causes the client to treat them 865 as binary files, which suppresses any newline munging it 866 otherwise might do. Alternatively, if it is set to "guess", 867 then the contents of the file are examined to decide if 868 it is binary, similar to 'core.autocrlf'. 869 870gitcvs.dbname:: 871 Database used by git-cvsserver to cache revision information 872 derived from the git repository. The exact meaning depends on the 873 used database driver, for SQLite (which is the default driver) this 874 is a filename. Supports variable substitution (see 875 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`). 876 Default: '%Ggitcvs.%m.sqlite' 877 878gitcvs.dbdriver:: 879 Used Perl DBI driver. You can specify any available driver 880 for this here, but it might not work. git-cvsserver is tested 881 with 'DBD::SQLite', reported to work with 'DBD::Pg', and 882 reported *not* to work with 'DBD::mysql'. Experimental feature. 883 May not contain double colons (`:`). Default: 'SQLite'. 884 See linkgit:git-cvsserver[1]. 885 886gitcvs.dbuser, gitcvs.dbpass:: 887 Database user and password. Only useful if setting 'gitcvs.dbdriver', 888 since SQLite has no concept of database users and/or passwords. 889 'gitcvs.dbuser' supports variable substitution (see 890 linkgit:git-cvsserver[1] for details). 891 892gitcvs.dbTableNamePrefix:: 893 Database table name prefix. Prepended to the names of any 894 database tables used, allowing a single database to be used 895 for several repositories. Supports variable substitution (see 896 linkgit:git-cvsserver[1] for details). Any non-alphabetic 897 characters will be replaced with underscores. 898 899All gitcvs variables except for 'gitcvs.usecrlfattr' and 900'gitcvs.allbinary' can also be specified as 901'gitcvs.<access_method>.<varname>' (where 'access_method' 902is one of "ext" and "pserver") to make them apply only for the given 903access method. 904 905gui.commitmsgwidth:: 906 Defines how wide the commit message window is in the 907 linkgit:git-gui[1]. "75" is the default. 908 909gui.diffcontext:: 910 Specifies how many context lines should be used in calls to diff 911 made by the linkgit:git-gui[1]. The default is "5". 912 913gui.encoding:: 914 Specifies the default encoding to use for displaying of 915 file contents in linkgit:git-gui[1] and linkgit:gitk[1]. 916 It can be overridden by setting the 'encoding' attribute 917 for relevant files (see linkgit:gitattributes[5]). 918 If this option is not set, the tools default to the 919 locale encoding. 920 921gui.matchtrackingbranch:: 922 Determines if new branches created with linkgit:git-gui[1] should 923 default to tracking remote branches with matching names or 924 not. Default: "false". 925 926gui.newbranchtemplate:: 927 Is used as suggested name when creating new branches using the 928 linkgit:git-gui[1]. 929 930gui.pruneduringfetch:: 931 "true" if linkgit:git-gui[1] should prune tracking branches when 932 performing a fetch. The default value is "false". 933 934gui.trustmtime:: 935 Determines if linkgit:git-gui[1] should trust the file modification 936 timestamp or not. By default the timestamps are not trusted. 937 938gui.spellingdictionary:: 939 Specifies the dictionary used for spell checking commit messages in 940 the linkgit:git-gui[1]. When set to "none" spell checking is turned 941 off. 942 943gui.fastcopyblame:: 944 If true, 'git gui blame' uses '-C' instead of '-C -C' for original 945 location detection. It makes blame significantly faster on huge 946 repositories at the expense of less thorough copy detection. 947 948gui.copyblamethreshold:: 949 Specifies the threshold to use in 'git gui blame' original location 950 detection, measured in alphanumeric characters. See the 951 linkgit:git-blame[1] manual for more information on copy detection. 952 953gui.blamehistoryctx:: 954 Specifies the radius of history context in days to show in 955 linkgit:gitk[1] for the selected commit, when the `Show History 956 Context` menu item is invoked from 'git gui blame'. If this 957 variable is set to zero, the whole history is shown. 958 959guitool.<name>.cmd:: 960 Specifies the shell command line to execute when the corresponding item 961 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is 962 mandatory for every tool. The command is executed from the root of 963 the working directory, and in the environment it receives the name of 964 the tool as 'GIT_GUITOOL', the name of the currently selected file as 965 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if 966 the head is detached, 'CUR_BRANCH' is empty). 967 968guitool.<name>.needsfile:: 969 Run the tool only if a diff is selected in the GUI. It guarantees 970 that 'FILENAME' is not empty. 971 972guitool.<name>.noconsole:: 973 Run the command silently, without creating a window to display its 974 output. 975 976guitool.<name>.norescan:: 977 Don't rescan the working directory for changes after the tool 978 finishes execution. 979 980guitool.<name>.confirm:: 981 Show a confirmation dialog before actually running the tool. 982 983guitool.<name>.argprompt:: 984 Request a string argument from the user, and pass it to the tool 985 through the 'ARGS' environment variable. Since requesting an 986 argument implies confirmation, the 'confirm' option has no effect 987 if this is enabled. If the option is set to 'true', 'yes', or '1', 988 the dialog uses a built-in generic prompt; otherwise the exact 989 value of the variable is used. 990 991guitool.<name>.revprompt:: 992 Request a single valid revision from the user, and set the 993 'REVISION' environment variable. In other aspects this option 994 is similar to 'argprompt', and can be used together with it. 995 996guitool.<name>.revunmerged:: 997 Show only unmerged branches in the 'revprompt' subdialog. 998 This is useful for tools similar to merge or rebase, but not 999 for things like checkout or reset.10001001guitool.<name>.title::1002 Specifies the title to use for the prompt dialog. The default1003 is the tool name.10041005guitool.<name>.prompt::1006 Specifies the general prompt string to display at the top of1007 the dialog, before subsections for 'argprompt' and 'revprompt'.1008 The default value includes the actual command.10091010help.browser::1011 Specify the browser that will be used to display help in the1012 'web' format. See linkgit:git-help[1].10131014help.format::1015 Override the default help format used by linkgit:git-help[1].1016 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1017 the default. 'web' and 'html' are the same.10181019help.autocorrect::1020 Automatically correct and execute mistyped commands after1021 waiting for the given number of deciseconds (0.1 sec). If more1022 than one command can be deduced from the entered text, nothing1023 will be executed. If the value of this option is negative,1024 the corrected command will be executed immediately. If the1025 value is 0 - the command will be just shown but not executed.1026 This is the default.10271028http.proxy::1029 Override the HTTP proxy, normally configured using the 'http_proxy'1030 environment variable (see linkgit:curl[1]). This can be overridden1031 on a per-remote basis; see remote.<name>.proxy10321033http.sslVerify::1034 Whether to verify the SSL certificate when fetching or pushing1035 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1036 variable.10371038http.sslCert::1039 File containing the SSL certificate when fetching or pushing1040 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1041 variable.10421043http.sslKey::1044 File containing the SSL private key when fetching or pushing1045 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1046 variable.10471048http.sslCertPasswordProtected::1049 Enable git's password prompt for the SSL certificate. Otherwise1050 OpenSSL will prompt the user, possibly many times, if the1051 certificate or private key is encrypted. Can be overridden by the1052 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.10531054http.sslCAInfo::1055 File containing the certificates to verify the peer with when1056 fetching or pushing over HTTPS. Can be overridden by the1057 'GIT_SSL_CAINFO' environment variable.10581059http.sslCAPath::1060 Path containing files with the CA certificates to verify the peer1061 with when fetching or pushing over HTTPS. Can be overridden1062 by the 'GIT_SSL_CAPATH' environment variable.10631064http.maxRequests::1065 How many HTTP requests to launch in parallel. Can be overridden1066 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.10671068http.lowSpeedLimit, http.lowSpeedTime::1069 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1070 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1071 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1072 'GIT_HTTP_LOW_SPEED_TIME' environment variables.10731074http.noEPSV::1075 A boolean which disables using of EPSV ftp command by curl.1076 This can helpful with some "poor" ftp servers which don't1077 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1078 environment variable. Default is false (curl will use EPSV).10791080i18n.commitEncoding::1081 Character encoding the commit messages are stored in; git itself1082 does not care per se, but this information is necessary e.g. when1083 importing commits from emails or in the gitk graphical history1084 browser (and possibly at other places in the future or in other1085 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.10861087i18n.logOutputEncoding::1088 Character encoding the commit messages are converted to when1089 running 'git-log' and friends.10901091imap::1092 The configuration variables in the 'imap' section are described1093 in linkgit:git-imap-send[1].10941095instaweb.browser::1096 Specify the program that will be used to browse your working1097 repository in gitweb. See linkgit:git-instaweb[1].10981099instaweb.httpd::1100 The HTTP daemon command-line to start gitweb on your working1101 repository. See linkgit:git-instaweb[1].11021103instaweb.local::1104 If true the web server started by linkgit:git-instaweb[1] will1105 be bound to the local IP (127.0.0.1).11061107instaweb.modulepath::1108 The module path for an apache httpd used by linkgit:git-instaweb[1].11091110instaweb.port::1111 The port number to bind the gitweb httpd to. See1112 linkgit:git-instaweb[1].11131114interactive.singlekey::1115 In interactive programs, allow the user to provide one-letter1116 input with a single key (i.e., without hitting enter).1117 Currently this is used only by the `\--patch` mode of1118 linkgit:git-add[1]. Note that this setting is silently1119 ignored if portable keystroke input is not available.11201121log.date::1122 Set default date-time mode for the log command. Setting log.date1123 value is similar to using 'git-log'\'s --date option. The value is one of the1124 following alternatives: {relative,local,default,iso,rfc,short}.1125 See linkgit:git-log[1].11261127log.showroot::1128 If true, the initial commit will be shown as a big creation event.1129 This is equivalent to a diff against an empty tree.1130 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1131 normally hide the root commit will now show it. True by default.11321133mailmap.file::1134 The location of an augmenting mailmap file. The default1135 mailmap, located in the root of the repository, is loaded1136 first, then the mailmap file pointed to by this variable.1137 The location of the mailmap file may be in a repository1138 subdirectory, or somewhere outside of the repository itself.1139 See linkgit:git-shortlog[1] and linkgit:git-blame[1].11401141man.viewer::1142 Specify the programs that may be used to display help in the1143 'man' format. See linkgit:git-help[1].11441145man.<tool>.cmd::1146 Specify the command to invoke the specified man viewer. The1147 specified command is evaluated in shell with the man page1148 passed as argument. (See linkgit:git-help[1].)11491150man.<tool>.path::1151 Override the path for the given tool that may be used to1152 display help in the 'man' format. See linkgit:git-help[1].11531154include::merge-config.txt[]11551156mergetool.<tool>.path::1157 Override the path for the given tool. This is useful in case1158 your tool is not in the PATH.11591160mergetool.<tool>.cmd::1161 Specify the command to invoke the specified merge tool. The1162 specified command is evaluated in shell with the following1163 variables available: 'BASE' is the name of a temporary file1164 containing the common base of the files to be merged, if available;1165 'LOCAL' is the name of a temporary file containing the contents of1166 the file on the current branch; 'REMOTE' is the name of a temporary1167 file containing the contents of the file from the branch being1168 merged; 'MERGED' contains the name of the file to which the merge1169 tool should write the results of a successful merge.11701171mergetool.<tool>.trustExitCode::1172 For a custom merge command, specify whether the exit code of1173 the merge command can be used to determine whether the merge was1174 successful. If this is not set to true then the merge target file1175 timestamp is checked and the merge assumed to have been successful1176 if the file has been updated, otherwise the user is prompted to1177 indicate the success of the merge.11781179mergetool.keepBackup::1180 After performing a merge, the original file with conflict markers1181 can be saved as a file with a `.orig` extension. If this variable1182 is set to `false` then this file is not preserved. Defaults to1183 `true` (i.e. keep the backup files).11841185mergetool.keepTemporaries::1186 When invoking a custom merge tool, git uses a set of temporary1187 files to pass to the tool. If the tool returns an error and this1188 variable is set to `true`, then these temporary files will be1189 preserved, otherwise they will be removed after the tool has1190 exited. Defaults to `false`.11911192mergetool.prompt::1193 Prompt before each invocation of the merge resolution program.11941195pack.window::1196 The size of the window used by linkgit:git-pack-objects[1] when no1197 window size is given on the command line. Defaults to 10.11981199pack.depth::1200 The maximum delta depth used by linkgit:git-pack-objects[1] when no1201 maximum depth is given on the command line. Defaults to 50.12021203pack.windowMemory::1204 The window memory size limit used by linkgit:git-pack-objects[1]1205 when no limit is given on the command line. The value can be1206 suffixed with "k", "m", or "g". Defaults to 0, meaning no1207 limit.12081209pack.compression::1210 An integer -1..9, indicating the compression level for objects1211 in a pack file. -1 is the zlib default. 0 means no1212 compression, and 1..9 are various speed/size tradeoffs, 9 being1213 slowest. If not set, defaults to core.compression. If that is1214 not set, defaults to -1, the zlib default, which is "a default1215 compromise between speed and compression (currently equivalent1216 to level 6)."12171218pack.deltaCacheSize::1219 The maximum memory in bytes used for caching deltas in1220 linkgit:git-pack-objects[1].1221 A value of 0 means no limit. Defaults to 0.12221223pack.deltaCacheLimit::1224 The maximum size of a delta, that is cached in1225 linkgit:git-pack-objects[1]. Defaults to 1000.12261227pack.threads::1228 Specifies the number of threads to spawn when searching for best1229 delta matches. This requires that linkgit:git-pack-objects[1]1230 be compiled with pthreads otherwise this option is ignored with a1231 warning. This is meant to reduce packing time on multiprocessor1232 machines. The required amount of memory for the delta search window1233 is however multiplied by the number of threads.1234 Specifying 0 will cause git to auto-detect the number of CPU's1235 and set the number of threads accordingly.12361237pack.indexVersion::1238 Specify the default pack index version. Valid values are 1 for1239 legacy pack index used by Git versions prior to 1.5.2, and 2 for1240 the new pack index with capabilities for packs larger than 4 GB1241 as well as proper protection against the repacking of corrupted1242 packs. Version 2 is the default. Note that version 2 is enforced1243 and this config option ignored whenever the corresponding pack is1244 larger than 2 GB.1245+1246If you have an old git that does not understand the version 2 `{asterisk}.idx` file,1247cloning or fetching over a non native protocol (e.g. "http" and "rsync")1248that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the1249other side may give you a repository that cannot be accessed with your1250older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,1251you can use linkgit:git-index-pack[1] on the *.pack file to regenerate1252the `{asterisk}.idx` file.12531254pack.packSizeLimit::1255 The default maximum size of a pack. This setting only affects1256 packing to a file, i.e. the git:// protocol is unaffected. It1257 can be overridden by the `\--max-pack-size` option of1258 linkgit:git-repack[1].12591260pager.<cmd>::1261 Allows turning on or off pagination of the output of a1262 particular git subcommand when writing to a tty. If1263 `\--paginate` or `\--no-pager` is specified on the command line,1264 it takes precedence over this option. To disable pagination for1265 all commands, set `core.pager` or `GIT_PAGER` to `cat`.12661267pull.octopus::1268 The default merge strategy to use when pulling multiple branches1269 at once.12701271pull.twohead::1272 The default merge strategy to use when pulling a single branch.12731274push.default::1275 Defines the action git push should take if no refspec is given1276 on the command line, no refspec is configured in the remote, and1277 no refspec is implied by any of the options given on the command1278 line. Possible values are:1279+1280* `nothing` do not push anything.1281* `matching` push all matching branches.1282 All branches having the same name in both ends are considered to be1283 matching. This is the default.1284* `tracking` push the current branch to its upstream branch.1285* `current` push the current branch to a branch of the same name.12861287rebase.stat::1288 Whether to show a diffstat of what changed upstream since the last1289 rebase. False by default.12901291receive.fsckObjects::1292 If it is set to true, git-receive-pack will check all received1293 objects. It will abort in the case of a malformed object or a1294 broken link. The result of an abort are only dangling objects.1295 Defaults to false.12961297receive.unpackLimit::1298 If the number of objects received in a push is below this1299 limit then the objects will be unpacked into loose object1300 files. However if the number of received objects equals or1301 exceeds this limit then the received pack will be stored as1302 a pack, after adding any missing delta bases. Storing the1303 pack from a push can make the push operation complete faster,1304 especially on slow filesystems. If not set, the value of1305 `transfer.unpackLimit` is used instead.13061307receive.denyDeletes::1308 If set to true, git-receive-pack will deny a ref update that deletes1309 the ref. Use this to prevent such a ref deletion via a push.13101311receive.denyCurrentBranch::1312 If set to true or "refuse", receive-pack will deny a ref update1313 to the currently checked out branch of a non-bare repository.1314 Such a push is potentially dangerous because it brings the HEAD1315 out of sync with the index and working tree. If set to "warn",1316 print a warning of such a push to stderr, but allow the push to1317 proceed. If set to false or "ignore", allow such pushes with no1318 message. Defaults to "warn".13191320receive.denyNonFastForwards::1321 If set to true, git-receive-pack will deny a ref update which is1322 not a fast forward. Use this to prevent such an update via a push,1323 even if that push is forced. This configuration variable is1324 set when initializing a shared repository.13251326remote.<name>.url::1327 The URL of a remote repository. See linkgit:git-fetch[1] or1328 linkgit:git-push[1].13291330remote.<name>.pushurl::1331 The push URL of a remote repository. See linkgit:git-push[1].13321333remote.<name>.proxy::1334 For remotes that require curl (http, https and ftp), the URL to1335 the proxy to use for that remote. Set to the empty string to1336 disable proxying for that remote.13371338remote.<name>.fetch::1339 The default set of "refspec" for linkgit:git-fetch[1]. See1340 linkgit:git-fetch[1].13411342remote.<name>.push::1343 The default set of "refspec" for linkgit:git-push[1]. See1344 linkgit:git-push[1].13451346remote.<name>.mirror::1347 If true, pushing to this remote will automatically behave1348 as if the `\--mirror` option was given on the command line.13491350remote.<name>.skipDefaultUpdate::1351 If true, this remote will be skipped by default when updating1352 using the update subcommand of linkgit:git-remote[1].13531354remote.<name>.receivepack::1355 The default program to execute on the remote side when pushing. See1356 option \--receive-pack of linkgit:git-push[1].13571358remote.<name>.uploadpack::1359 The default program to execute on the remote side when fetching. See1360 option \--upload-pack of linkgit:git-fetch-pack[1].13611362remote.<name>.tagopt::1363 Setting this value to \--no-tags disables automatic tag following when1364 fetching from remote <name>13651366remotes.<group>::1367 The list of remotes which are fetched by "git remote update1368 <group>". See linkgit:git-remote[1].13691370repack.usedeltabaseoffset::1371 By default, linkgit:git-repack[1] creates packs that use1372 delta-base offset. If you need to share your repository with1373 git older than version 1.4.4, either directly or via a dumb1374 protocol such as http, then you need to set this option to1375 "false" and repack. Access from old git versions over the1376 native protocol are unaffected by this option.13771378rerere.autoupdate::1379 When set to true, `git-rerere` updates the index with the1380 resulting contents after it cleanly resolves conflicts using1381 previously recorded resolution. Defaults to false.13821383rerere.enabled::1384 Activate recording of resolved conflicts, so that identical1385 conflict hunks can be resolved automatically, should they1386 be encountered again. linkgit:git-rerere[1] command is by1387 default enabled if you create `rr-cache` directory under1388 `$GIT_DIR`, but can be disabled by setting this option to false.13891390sendemail.identity::1391 A configuration identity. When given, causes values in the1392 'sendemail.<identity>' subsection to take precedence over1393 values in the 'sendemail' section. The default identity is1394 the value of 'sendemail.identity'.13951396sendemail.smtpencryption::1397 See linkgit:git-send-email[1] for description. Note that this1398 setting is not subject to the 'identity' mechanism.13991400sendemail.smtpssl::1401 Deprecated alias for 'sendemail.smtpencryption = ssl'.14021403sendemail.<identity>.*::1404 Identity-specific versions of the 'sendemail.*' parameters1405 found below, taking precedence over those when the this1406 identity is selected, through command-line or1407 'sendemail.identity'.14081409sendemail.aliasesfile::1410sendemail.aliasfiletype::1411sendemail.bcc::1412sendemail.cc::1413sendemail.cccmd::1414sendemail.chainreplyto::1415sendemail.confirm::1416sendemail.envelopesender::1417sendemail.from::1418sendemail.multiedit::1419sendemail.signedoffbycc::1420sendemail.smtppass::1421sendemail.suppresscc::1422sendemail.suppressfrom::1423sendemail.to::1424sendemail.smtpserver::1425sendemail.smtpserverport::1426sendemail.smtpuser::1427sendemail.thread::1428sendemail.validate::1429 See linkgit:git-send-email[1] for description.14301431sendemail.signedoffcc::1432 Deprecated alias for 'sendemail.signedoffbycc'.14331434showbranch.default::1435 The default set of branches for linkgit:git-show-branch[1].1436 See linkgit:git-show-branch[1].14371438status.relativePaths::1439 By default, linkgit:git-status[1] shows paths relative to the1440 current directory. Setting this variable to `false` shows paths1441 relative to the repository root (this was the default for git1442 prior to v1.5.4).14431444status.showUntrackedFiles::1445 By default, linkgit:git-status[1] and linkgit:git-commit[1] show1446 files which are not currently tracked by Git. Directories which1447 contain only untracked files, are shown with the directory name1448 only. Showing untracked files means that Git needs to lstat() all1449 all the files in the whole repository, which might be slow on some1450 systems. So, this variable controls how the commands displays1451 the untracked files. Possible values are:1452+1453--1454 - 'no' - Show no untracked files1455 - 'normal' - Shows untracked files and directories1456 - 'all' - Shows also individual files in untracked directories.1457--1458+1459If this variable is not specified, it defaults to 'normal'.1460This variable can be overridden with the -u|--untracked-files option1461of linkgit:git-status[1] and linkgit:git-commit[1].14621463tar.umask::1464 This variable can be used to restrict the permission bits of1465 tar archive entries. The default is 0002, which turns off the1466 world write bit. The special value "user" indicates that the1467 archiving user's umask will be used instead. See umask(2) and1468 linkgit:git-archive[1].14691470transfer.unpackLimit::1471 When `fetch.unpackLimit` or `receive.unpackLimit` are1472 not set, the value of this variable is used instead.1473 The default value is 100.14741475url.<base>.insteadOf::1476 Any URL that starts with this value will be rewritten to1477 start, instead, with <base>. In cases where some site serves a1478 large number of repositories, and serves them with multiple1479 access methods, and some users need to use different access1480 methods, this feature allows people to specify any of the1481 equivalent URLs and have git automatically rewrite the URL to1482 the best alternative for the particular user, even for a1483 never-before-seen repository on the site. When more than one1484 insteadOf strings match a given URL, the longest match is used.14851486user.email::1487 Your email address to be recorded in any newly created commits.1488 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and1489 'EMAIL' environment variables. See linkgit:git-commit-tree[1].14901491user.name::1492 Your full name to be recorded in any newly created commits.1493 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'1494 environment variables. See linkgit:git-commit-tree[1].14951496user.signingkey::1497 If linkgit:git-tag[1] is not selecting the key you want it to1498 automatically when creating a signed tag, you can override the1499 default selection with this variable. This option is passed1500 unchanged to gpg's --local-user parameter, so you may specify a key1501 using any method that gpg supports.15021503web.browser::1504 Specify a web browser that may be used by some commands.1505 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]1506 may use it.