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 (and the remainder of the line after the section 53header) are recognized as setting variables, in the form 54'name = value'. If there is no equal sign on the line, the entire line 55is taken as 'name' and the variable is recognized as boolean "true". 56The variable names are case-insensitive and only alphanumeric 57characters and `-` are allowed. There can be more than one value 58for a given variable; we say then that variable is multivalued. 59 60Leading and trailing whitespace in a variable value is discarded. 61Internal whitespace within a variable value is retained verbatim. 62 63The values following the equals sign in variable assign are all either 64a string, an integer, or a boolean. Boolean values may be given as yes/no, 650/1, true/false or on/off. Case is not significant in boolean values, when 66converting value to the canonical form using '--bool' type specifier; 67'git config' will ensure that the output is "true" or "false". 68 69String values may be entirely or partially enclosed in double quotes. 70You need to enclose variable values in double quotes if you want to 71preserve leading or trailing whitespace, or if the variable value contains 72comment characters (i.e. it contains '#' or ';'). 73Double quote `"` and backslash `\` characters in variable values must 74be escaped: use `\"` for `"` and `\\` for `\`. 75 76The following escape sequences (beside `\"` and `\\`) are recognized: 77`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) 78and `\b` for backspace (BS). No other char escape sequence, nor octal 79char sequences are valid. 80 81Variable values ending in a `\` are continued on the next line in the 82customary UNIX fashion. 83 84Some variables may require a special value format. 85 86Example 87~~~~~~~ 88 89 # Core variables 90 [core] 91 ; Don't trust file modes 92 filemode = false 93 94 # Our diff algorithm 95 [diff] 96 external = /usr/local/bin/diff-wrapper 97 renames = true 98 99 [branch "devel"] 100 remote = origin 101 merge = refs/heads/devel 102 103 # Proxy settings 104 [core] 105 gitProxy="ssh" for "kernel.org" 106 gitProxy=default-proxy ; for the rest 107 108Variables 109~~~~~~~~~ 110 111Note that this list is non-comprehensive and not necessarily complete. 112For command-specific variables, you will find a more detailed description 113in the appropriate manual page. You will find a description of non-core 114porcelain configuration variables in the respective porcelain documentation. 115 116advice.*:: 117 When set to 'true', display the given optional help message. 118 When set to 'false', do not display. The configuration variables 119 are: 120+ 121-- 122 pushNonFastForward:: 123 Advice shown when linkgit:git-push[1] refuses 124 non-fast-forward refs. Default: true. 125 statusHints:: 126 Directions on how to stage/unstage/add shown in the 127 output of linkgit:git-status[1] and the template shown 128 when writing commit messages. Default: true. 129 commitBeforeMerge:: 130 Advice shown when linkgit:git-merge[1] refuses to 131 merge to avoid overwritting local changes. 132 Default: true. 133 resolveConflict:: 134 Advices shown by various commands when conflicts 135 prevent the operation from being performed. 136 Default: true. 137 implicitIdentity:: 138 Advice on how to set your identity configuration when 139 your information is guessed from the system username and 140 domain name. Default: true. 141 142 detachedHead:: 143 Advice shown when you used linkgit::git-checkout[1] to 144 move to the detach HEAD state, to instruct how to create 145 a local branch after the fact. Default: true. 146-- 147 148core.fileMode:: 149 If false, the executable bit differences between the index and 150 the working copy are ignored; useful on broken filesystems like FAT. 151 See linkgit:git-update-index[1]. 152+ 153The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 154will probe and set core.fileMode false if appropriate when the 155repository is created. 156 157core.ignoreCygwinFSTricks:: 158 This option is only used by Cygwin implementation of Git. If false, 159 the Cygwin stat() and lstat() functions are used. This may be useful 160 if your repository consists of a few separate directories joined in 161 one hierarchy using Cygwin mount. If true, Git uses native Win32 API 162 whenever it is possible and falls back to Cygwin functions only to 163 handle symbol links. The native mode is more than twice faster than 164 normal Cygwin l/stat() functions. True by default, unless core.filemode 165 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's 166 POSIX emulation is required to support core.filemode. 167 168core.ignorecase:: 169 If true, this option enables various workarounds to enable 170 git to work better on filesystems that are not case sensitive, 171 like FAT. For example, if a directory listing finds 172 "makefile" when git expects "Makefile", git will assume 173 it is really the same file, and continue to remember it as 174 "Makefile". 175+ 176The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 177will probe and set core.ignorecase true if appropriate when the repository 178is created. 179 180core.trustctime:: 181 If false, the ctime differences between the index and the 182 working copy are ignored; useful when the inode change time 183 is regularly modified by something outside Git (file system 184 crawlers and some backup systems). 185 See linkgit:git-update-index[1]. True by default. 186 187core.quotepath:: 188 The commands that output paths (e.g. 'ls-files', 189 'diff'), when not given the `-z` option, will quote 190 "unusual" characters in the pathname by enclosing the 191 pathname in a double-quote pair and with backslashes the 192 same way strings in C source code are quoted. If this 193 variable is set to false, the bytes higher than 0x80 are 194 not quoted but output as verbatim. Note that double 195 quote, backslash and control characters are always 196 quoted without `-z` regardless of the setting of this 197 variable. 198 199core.eol:: 200 Sets the line ending type to use in the working directory for 201 files that have the `text` property set. Alternatives are 202 'lf', 'crlf' and 'native', which uses the platform's native 203 line ending. The default value is `native`. See 204 linkgit:gitattributes[5] for more information on end-of-line 205 conversion. 206 207core.safecrlf:: 208 If true, makes git check if converting `CRLF` is reversible when 209 end-of-line conversion is active. Git will verify if a command 210 modifies a file in the work tree either directly or indirectly. 211 For example, committing a file followed by checking out the 212 same file should yield the original file in the work tree. If 213 this is not the case for the current setting of 214 `core.autocrlf`, git will reject the file. The variable can 215 be set to "warn", in which case git will only warn about an 216 irreversible conversion but continue the operation. 217+ 218CRLF conversion bears a slight chance of corrupting data. 219When it is enabled, git will convert CRLF to LF during commit and LF to 220CRLF during checkout. A file that contains a mixture of LF and 221CRLF before the commit cannot be recreated by git. For text 222files this is the right thing to do: it corrects line endings 223such that we have only LF line endings in the repository. 224But for binary files that are accidentally classified as text the 225conversion can corrupt data. 226+ 227If you recognize such corruption early you can easily fix it by 228setting the conversion type explicitly in .gitattributes. Right 229after committing you still have the original file in your work 230tree and this file is not yet corrupted. You can explicitly tell 231git that this file is binary and git will handle the file 232appropriately. 233+ 234Unfortunately, the desired effect of cleaning up text files with 235mixed line endings and the undesired effect of corrupting binary 236files cannot be distinguished. In both cases CRLFs are removed 237in an irreversible way. For text files this is the right thing 238to do because CRLFs are line endings, while for binary files 239converting CRLFs corrupts data. 240+ 241Note, this safety check does not mean that a checkout will generate a 242file identical to the original file for a different setting of 243`core.eol` and `core.autocrlf`, but only for the current one. For 244example, a text file with `LF` would be accepted with `core.eol=lf` 245and could later be checked out with `core.eol=crlf`, in which case the 246resulting file would contain `CRLF`, although the original file 247contained `LF`. However, in both work trees the line endings would be 248consistent, that is either all `LF` or all `CRLF`, but never mixed. A 249file with mixed line endings would be reported by the `core.safecrlf` 250mechanism. 251 252core.autocrlf:: 253 Setting this variable to "true" is almost the same as setting 254 the `text` attribute to "auto" on all files except that text 255 files are not guaranteed to be normalized: files that contain 256 `CRLF` in the repository will not be touched. Use this 257 setting if you want to have `CRLF` line endings in your 258 working directory even though the repository does not have 259 normalized line endings. This variable can be set to 'input', 260 in which case no output conversion is performed. 261 262core.symlinks:: 263 If false, symbolic links are checked out as small plain files that 264 contain the link text. linkgit:git-update-index[1] and 265 linkgit:git-add[1] will not change the recorded type to regular 266 file. Useful on filesystems like FAT that do not support 267 symbolic links. 268+ 269The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 270will probe and set core.symlinks false if appropriate when the repository 271is created. 272 273core.gitProxy:: 274 A "proxy command" to execute (as 'command host port') instead 275 of establishing direct connection to the remote server when 276 using the git protocol for fetching. If the variable value is 277 in the "COMMAND for DOMAIN" format, the command is applied only 278 on hostnames ending with the specified domain string. This variable 279 may be set multiple times and is matched in the given order; 280 the first match wins. 281+ 282Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 283(which always applies universally, without the special "for" 284handling). 285+ 286The special string `none` can be used as the proxy command to 287specify that no proxy be used for a given domain pattern. 288This is useful for excluding servers inside a firewall from 289proxy use, while defaulting to a common proxy for external domains. 290 291core.ignoreStat:: 292 If true, commands which modify both the working tree and the index 293 will mark the updated paths with the "assume unchanged" bit in the 294 index. These marked files are then assumed to stay unchanged in the 295 working copy, until you mark them otherwise manually - Git will not 296 detect the file changes by lstat() calls. This is useful on systems 297 where those are very slow, such as Microsoft Windows. 298 See linkgit:git-update-index[1]. 299 False by default. 300 301core.preferSymlinkRefs:: 302 Instead of the default "symref" format for HEAD 303 and other symbolic reference files, use symbolic links. 304 This is sometimes needed to work with old scripts that 305 expect HEAD to be a symbolic link. 306 307core.bare:: 308 If true this repository is assumed to be 'bare' and has no 309 working directory associated with it. If this is the case a 310 number of commands that require a working directory will be 311 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 312+ 313This setting is automatically guessed by linkgit:git-clone[1] or 314linkgit:git-init[1] when the repository was created. By default a 315repository that ends in "/.git" is assumed to be not bare (bare = 316false), while all other repositories are assumed to be bare (bare 317= true). 318 319core.worktree:: 320 Set the path to the root of the work tree. 321 This can be overridden by the GIT_WORK_TREE environment 322 variable and the '--work-tree' command line option. It can be 323 an absolute path or a relative path to the .git directory, 324 either specified by --git-dir or GIT_DIR, or automatically 325 discovered. 326 If --git-dir or GIT_DIR are specified but none of 327 --work-tree, GIT_WORK_TREE and core.worktree is specified, 328 the current working directory is regarded as the root of the 329 work tree. 330+ 331Note that this variable is honored even when set in a configuration 332file in a ".git" subdirectory of a directory, and its value differs 333from the latter directory (e.g. "/path/to/.git/config" has 334core.worktree set to "/different/path"), which is most likely a 335misconfiguration. Running git commands in "/path/to" directory will 336still use "/different/path" as the root of the work tree and can cause 337great confusion to the users. 338 339core.logAllRefUpdates:: 340 Enable the reflog. Updates to a ref <ref> is logged to the file 341 "$GIT_DIR/logs/<ref>", by appending the new and old 342 SHA1, the date/time and the reason of the update, but 343 only when the file exists. If this configuration 344 variable is set to true, missing "$GIT_DIR/logs/<ref>" 345 file is automatically created for branch heads. 346+ 347This information can be used to determine what commit 348was the tip of a branch "2 days ago". 349+ 350This value is true by default in a repository that has 351a working directory associated with it, and false by 352default in a bare repository. 353 354core.repositoryFormatVersion:: 355 Internal variable identifying the repository format and layout 356 version. 357 358core.sharedRepository:: 359 When 'group' (or 'true'), the repository is made shareable between 360 several users in a group (making sure all the files and objects are 361 group-writable). When 'all' (or 'world' or 'everybody'), the 362 repository will be readable by all users, additionally to being 363 group-shareable. When 'umask' (or 'false'), git will use permissions 364 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 365 files in the repository will have this mode value. '0xxx' will override 366 user's umask value (whereas the other options will only override 367 requested parts of the user's umask value). Examples: '0660' will make 368 the repo read/write-able for the owner and group, but inaccessible to 369 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 370 repository that is group-readable but not group-writable. 371 See linkgit:git-init[1]. False by default. 372 373core.warnAmbiguousRefs:: 374 If true, git will warn you if the ref name you passed it is ambiguous 375 and might match multiple refs in the .git/refs/ tree. True by default. 376 377core.compression:: 378 An integer -1..9, indicating a default compression level. 379 -1 is the zlib default. 0 means no compression, 380 and 1..9 are various speed/size tradeoffs, 9 being slowest. 381 If set, this provides a default to other compression variables, 382 such as 'core.loosecompression' and 'pack.compression'. 383 384core.loosecompression:: 385 An integer -1..9, indicating the compression level for objects that 386 are not in a pack file. -1 is the zlib default. 0 means no 387 compression, and 1..9 are various speed/size tradeoffs, 9 being 388 slowest. If not set, defaults to core.compression. If that is 389 not set, defaults to 1 (best speed). 390 391core.packedGitWindowSize:: 392 Number of bytes of a pack file to map into memory in a 393 single mapping operation. Larger window sizes may allow 394 your system to process a smaller number of large pack files 395 more quickly. Smaller window sizes will negatively affect 396 performance due to increased calls to the operating system's 397 memory manager, but may improve performance when accessing 398 a large number of large pack files. 399+ 400Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 401MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 402be reasonable for all users/operating systems. You probably do 403not need to adjust this value. 404+ 405Common unit suffixes of 'k', 'm', or 'g' are supported. 406 407core.packedGitLimit:: 408 Maximum number of bytes to map simultaneously into memory 409 from pack files. If Git needs to access more than this many 410 bytes at once to complete an operation it will unmap existing 411 regions to reclaim virtual address space within the process. 412+ 413Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 414This should be reasonable for all users/operating systems, except on 415the largest projects. You probably do not need to adjust this value. 416+ 417Common unit suffixes of 'k', 'm', or 'g' are supported. 418 419core.deltaBaseCacheLimit:: 420 Maximum number of bytes to reserve for caching base objects 421 that multiple deltafied objects reference. By storing the 422 entire decompressed base objects in a cache Git is able 423 to avoid unpacking and decompressing frequently used base 424 objects multiple times. 425+ 426Default is 16 MiB on all platforms. This should be reasonable 427for all users/operating systems, except on the largest projects. 428You probably do not need to adjust this value. 429+ 430Common unit suffixes of 'k', 'm', or 'g' are supported. 431 432core.bigFileThreshold:: 433 Files larger than this size are stored deflated, without 434 attempting delta compression. Storing large files without 435 delta compression avoids excessive memory usage, at the 436 slight expense of increased disk usage. 437+ 438Default is 512 MiB on all platforms. This should be reasonable 439for most projects as source code and other text files can still 440be delta compressed, but larger binary media files won't be. 441+ 442Common unit suffixes of 'k', 'm', or 'g' are supported. 443+ 444Currently only linkgit:git-fast-import[1] honors this setting. 445 446core.excludesfile:: 447 In addition to '.gitignore' (per-directory) and 448 '.git/info/exclude', git looks into this file for patterns 449 of files which are not meant to be tracked. "{tilde}/" is expanded 450 to the value of `$HOME` and "{tilde}user/" to the specified user's 451 home directory. See linkgit:gitignore[5]. 452 453core.attributesfile:: 454 In addition to '.gitattributes' (per-directory) and 455 '.git/info/attributes', git looks into this file for attributes 456 (see linkgit:gitattributes[5]). Path expansions are made the same 457 way as for `core.excludesfile`. 458 459core.editor:: 460 Commands such as `commit` and `tag` that lets you edit 461 messages by launching an editor uses the value of this 462 variable when it is set, and the environment variable 463 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 464 465core.pager:: 466 The command that git will use to paginate output. Can 467 be overridden with the `GIT_PAGER` environment 468 variable. Note that git sets the `LESS` environment 469 variable to `FRSX` if it is unset when it runs the 470 pager. One can change these settings by setting the 471 `LESS` variable to some other value. Alternately, 472 these settings can be overridden on a project or 473 global basis by setting the `core.pager` option. 474 Setting `core.pager` has no affect on the `LESS` 475 environment variable behaviour above, so if you want 476 to override git's default settings this way, you need 477 to be explicit. For example, to disable the S option 478 in a backward compatible manner, set `core.pager` 479 to `less -+$LESS -FRX`. This will be passed to the 480 shell by git, which will translate the final command to 481 `LESS=FRSX less -+FRSX -FRX`. 482 483core.whitespace:: 484 A comma separated list of common whitespace problems to 485 notice. 'git diff' will use `color.diff.whitespace` to 486 highlight them, and 'git apply --whitespace=error' will 487 consider them as errors. You can prefix `-` to disable 488 any of them (e.g. `-trailing-space`): 489+ 490* `blank-at-eol` treats trailing whitespaces at the end of the line 491 as an error (enabled by default). 492* `space-before-tab` treats a space character that appears immediately 493 before a tab character in the initial indent part of the line as an 494 error (enabled by default). 495* `indent-with-non-tab` treats a line that is indented with 8 or more 496 space characters as an error (not enabled by default). 497* `tab-in-indent` treats a tab character in the initial indent part of 498 the line as an error (not enabled by default). 499* `blank-at-eof` treats blank lines added at the end of file as an error 500 (enabled by default). 501* `trailing-space` is a short-hand to cover both `blank-at-eol` and 502 `blank-at-eof`. 503* `cr-at-eol` treats a carriage-return at the end of line as 504 part of the line terminator, i.e. with it, `trailing-space` 505 does not trigger if the character before such a carriage-return 506 is not a whitespace (not enabled by default). 507 508core.fsyncobjectfiles:: 509 This boolean will enable 'fsync()' when writing object files. 510+ 511This is a total waste of time and effort on a filesystem that orders 512data writes properly, but can be useful for filesystems that do not use 513journalling (traditional UNIX filesystems) or that only journal metadata 514and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 515 516core.preloadindex:: 517 Enable parallel index preload for operations like 'git diff' 518+ 519This can speed up operations like 'git diff' and 'git status' especially 520on filesystems like NFS that have weak caching semantics and thus 521relatively high IO latencies. With this set to 'true', git will do the 522index comparison to the filesystem data in parallel, allowing 523overlapping IO's. 524 525core.createObject:: 526 You can set this to 'link', in which case a hardlink followed by 527 a delete of the source are used to make sure that object creation 528 will not overwrite existing objects. 529+ 530On some file system/operating system combinations, this is unreliable. 531Set this config setting to 'rename' there; However, This will remove the 532check that makes sure that existing object files will not get overwritten. 533 534core.notesRef:: 535 When showing commit messages, also show notes which are stored in 536 the given ref. The ref must be fully qualified. If the given 537 ref does not exist, it is not an error but means that no 538 notes should be printed. 539+ 540This setting defaults to "refs/notes/commits", and it can be overridden by 541the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1]. 542 543core.sparseCheckout:: 544 Enable "sparse checkout" feature. See section "Sparse checkout" in 545 linkgit:git-read-tree[1] for more information. 546 547add.ignore-errors:: 548 Tells 'git add' to continue adding files when some files cannot be 549 added due to indexing errors. Equivalent to the '--ignore-errors' 550 option of linkgit:git-add[1]. 551 552alias.*:: 553 Command aliases for the linkgit:git[1] command wrapper - e.g. 554 after defining "alias.last = cat-file commit HEAD", the invocation 555 "git last" is equivalent to "git cat-file commit HEAD". To avoid 556 confusion and troubles with script usage, aliases that 557 hide existing git commands are ignored. Arguments are split by 558 spaces, the usual shell quoting and escaping is supported. 559 quote pair and a backslash can be used to quote them. 560+ 561If the alias expansion is prefixed with an exclamation point, 562it will be treated as a shell command. For example, defining 563"alias.new = !gitk --all --not ORIG_HEAD", the invocation 564"git new" is equivalent to running the shell command 565"gitk --all --not ORIG_HEAD". Note that shell commands will be 566executed from the top-level directory of a repository, which may 567not necessarily be the current directory. 568 569am.keepcr:: 570 If true, git-am will call git-mailsplit for patches in mbox format 571 with parameter '--keep-cr'. In this case git-mailsplit will 572 not remove `\r` from lines ending with `\r\n`. Can be overrriden 573 by giving '--no-keep-cr' from the command line. 574 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 575 576apply.ignorewhitespace:: 577 When set to 'change', tells 'git apply' to ignore changes in 578 whitespace, in the same way as the '--ignore-space-change' 579 option. 580 When set to one of: no, none, never, false tells 'git apply' to 581 respect all whitespace differences. 582 See linkgit:git-apply[1]. 583 584apply.whitespace:: 585 Tells 'git apply' how to handle whitespaces, in the same way 586 as the '--whitespace' option. See linkgit:git-apply[1]. 587 588branch.autosetupmerge:: 589 Tells 'git branch' and 'git checkout' to set up new branches 590 so that linkgit:git-pull[1] will appropriately merge from the 591 starting point branch. Note that even if this option is not set, 592 this behavior can be chosen per-branch using the `--track` 593 and `--no-track` options. The valid settings are: `false` -- no 594 automatic setup is done; `true` -- automatic setup is done when the 595 starting point is a remote branch; `always` -- automatic setup is 596 done when the starting point is either a local branch or remote 597 branch. This option defaults to true. 598 599branch.autosetuprebase:: 600 When a new branch is created with 'git branch' or 'git checkout' 601 that tracks another branch, this variable tells git to set 602 up pull to rebase instead of merge (see "branch.<name>.rebase"). 603 When `never`, rebase is never automatically set to true. 604 When `local`, rebase is set to true for tracked branches of 605 other local branches. 606 When `remote`, rebase is set to true for tracked branches of 607 remote branches. 608 When `always`, rebase will be set to true for all tracking 609 branches. 610 See "branch.autosetupmerge" for details on how to set up a 611 branch to track another branch. 612 This option defaults to never. 613 614branch.<name>.remote:: 615 When in branch <name>, it tells 'git fetch' and 'git push' which 616 remote to fetch from/push to. It defaults to `origin` if no remote is 617 configured. `origin` is also used if you are not on any branch. 618 619branch.<name>.merge:: 620 Defines, together with branch.<name>.remote, the upstream branch 621 for the given branch. It tells 'git fetch'/'git pull' which 622 branch to merge and can also affect 'git push' (see push.default). 623 When in branch <name>, it tells 'git fetch' the default 624 refspec to be marked for merging in FETCH_HEAD. The value is 625 handled like the remote part of a refspec, and must match a 626 ref which is fetched from the remote given by 627 "branch.<name>.remote". 628 The merge information is used by 'git pull' (which at first calls 629 'git fetch') to lookup the default branch for merging. Without 630 this option, 'git pull' defaults to merge the first refspec fetched. 631 Specify multiple values to get an octopus merge. 632 If you wish to setup 'git pull' so that it merges into <name> from 633 another branch in the local repository, you can point 634 branch.<name>.merge to the desired branch, and use the special setting 635 `.` (a period) for branch.<name>.remote. 636 637branch.<name>.mergeoptions:: 638 Sets default options for merging into branch <name>. The syntax and 639 supported options are the same as those of linkgit:git-merge[1], but 640 option values containing whitespace characters are currently not 641 supported. 642 643branch.<name>.rebase:: 644 When true, rebase the branch <name> on top of the fetched branch, 645 instead of merging the default branch from the default remote when 646 "git pull" is run. 647 *NOTE*: this is a possibly dangerous operation; do *not* use 648 it unless you understand the implications (see linkgit:git-rebase[1] 649 for details). 650 651browser.<tool>.cmd:: 652 Specify the command to invoke the specified browser. The 653 specified command is evaluated in shell with the URLs passed 654 as arguments. (See linkgit:git-web--browse[1].) 655 656browser.<tool>.path:: 657 Override the path for the given tool that may be used to 658 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 659 working repository in gitweb (see linkgit:git-instaweb[1]). 660 661clean.requireForce:: 662 A boolean to make git-clean do nothing unless given -f 663 or -n. Defaults to true. 664 665color.branch:: 666 A boolean to enable/disable color in the output of 667 linkgit:git-branch[1]. May be set to `always`, 668 `false` (or `never`) or `auto` (or `true`), in which case colors are used 669 only when the output is to a terminal. Defaults to false. 670 671color.branch.<slot>:: 672 Use customized color for branch coloration. `<slot>` is one of 673 `current` (the current branch), `local` (a local branch), 674 `remote` (a tracking branch in refs/remotes/), `plain` (other 675 refs). 676+ 677The value for these configuration variables is a list of colors (at most 678two) and attributes (at most one), separated by spaces. The colors 679accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`, 680`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`, 681`blink` and `reverse`. The first color given is the foreground; the 682second is the background. The position of the attribute, if any, 683doesn't matter. 684 685color.diff:: 686 When set to `always`, always use colors in patch. 687 When false (or `never`), never. When set to `true` or `auto`, use 688 colors only when the output is to the terminal. Defaults to false. 689 690color.diff.<slot>:: 691 Use customized color for diff colorization. `<slot>` specifies 692 which part of the patch to use the specified color, and is one 693 of `plain` (context text), `meta` (metainformation), `frag` 694 (hunk header), 'func' (function in hunk header), `old` (removed lines), 695 `new` (added lines), `commit` (commit headers), or `whitespace` 696 (highlighting whitespace errors). The values of these variables may be 697 specified as in color.branch.<slot>. 698 699color.decorate.<slot>:: 700 Use customized color for 'git log --decorate' output. `<slot>` is one 701 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local 702 branches, remote tracking branches, tags, stash and HEAD, respectively. 703 704color.grep:: 705 When set to `always`, always highlight matches. When `false` (or 706 `never`), never. When set to `true` or `auto`, use color only 707 when the output is written to the terminal. Defaults to `false`. 708 709color.grep.<slot>:: 710 Use customized color for grep colorization. `<slot>` specifies which 711 part of the line to use the specified color, and is one of 712+ 713-- 714`context`;; 715 non-matching text in context lines (when using `-A`, `-B`, or `-C`) 716`filename`;; 717 filename prefix (when not using `-h`) 718`function`;; 719 function name lines (when using `-p`) 720`linenumber`;; 721 line number prefix (when using `-n`) 722`match`;; 723 matching text 724`selected`;; 725 non-matching text in selected lines 726`separator`;; 727 separators between fields on a line (`:`, `-`, and `=`) 728 and between hunks (`--`) 729-- 730+ 731The values of these variables may be specified as in color.branch.<slot>. 732 733color.interactive:: 734 When set to `always`, always use colors for interactive prompts 735 and displays (such as those used by "git-add --interactive"). 736 When false (or `never`), never. When set to `true` or `auto`, use 737 colors only when the output is to the terminal. Defaults to false. 738 739color.interactive.<slot>:: 740 Use customized color for 'git add --interactive' 741 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for 742 four distinct types of normal output from interactive 743 commands. The values of these variables may be specified as 744 in color.branch.<slot>. 745 746color.pager:: 747 A boolean to enable/disable colored output when the pager is in 748 use (default is true). 749 750color.showbranch:: 751 A boolean to enable/disable color in the output of 752 linkgit:git-show-branch[1]. May be set to `always`, 753 `false` (or `never`) or `auto` (or `true`), in which case colors are used 754 only when the output is to a terminal. Defaults to false. 755 756color.status:: 757 A boolean to enable/disable color in the output of 758 linkgit:git-status[1]. May be set to `always`, 759 `false` (or `never`) or `auto` (or `true`), in which case colors are used 760 only when the output is to a terminal. Defaults to false. 761 762color.status.<slot>:: 763 Use customized color for status colorization. `<slot>` is 764 one of `header` (the header text of the status message), 765 `added` or `updated` (files which are added but not committed), 766 `changed` (files which are changed but not added in the index), 767 `untracked` (files which are not tracked by git), or 768 `nobranch` (the color the 'no branch' warning is shown in, defaulting 769 to red). The values of these variables may be specified as in 770 color.branch.<slot>. 771 772color.ui:: 773 When set to `always`, always use colors in all git commands which 774 are capable of colored output. When false (or `never`), never. When 775 set to `true` or `auto`, use colors only when the output is to the 776 terminal. When more specific variables of color.* are set, they always 777 take precedence over this setting. Defaults to false. 778 779commit.status:: 780 A boolean to enable/disable inclusion of status information in the 781 commit message template when using an editor to prepare the commit 782 message. Defaults to true. 783 784commit.template:: 785 Specify a file to use as the template for new commit messages. 786 "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the 787 specified user's home directory. 788 789diff.autorefreshindex:: 790 When using 'git diff' to compare with work tree 791 files, do not consider stat-only change as changed. 792 Instead, silently run `git update-index --refresh` to 793 update the cached stat information for paths whose 794 contents in the work tree match the contents in the 795 index. This option defaults to true. Note that this 796 affects only 'git diff' Porcelain, and not lower level 797 'diff' commands such as 'git diff-files'. 798 799diff.external:: 800 If this config variable is set, diff generation is not 801 performed using the internal diff machinery, but using the 802 given command. Can be overridden with the `GIT_EXTERNAL_DIFF' 803 environment variable. The command is called with parameters 804 as described under "git Diffs" in linkgit:git[1]. Note: if 805 you want to use an external diff program only on a subset of 806 your files, you might want to use linkgit:gitattributes[5] instead. 807 808diff.mnemonicprefix:: 809 If set, 'git diff' uses a prefix pair that is different from the 810 standard "a/" and "b/" depending on what is being compared. When 811 this configuration is in effect, reverse diff output also swaps 812 the order of the prefixes: 813diff.noprefix:: 814 If set, 'git diff' does not show any source or destination prefix. 815`git diff`;; 816 compares the (i)ndex and the (w)ork tree; 817`git diff HEAD`;; 818 compares a (c)ommit and the (w)ork tree; 819`git diff --cached`;; 820 compares a (c)ommit and the (i)ndex; 821`git diff HEAD:file1 file2`;; 822 compares an (o)bject and a (w)ork tree entity; 823`git diff --no-index a b`;; 824 compares two non-git things (1) and (2). 825 826diff.renameLimit:: 827 The number of files to consider when performing the copy/rename 828 detection; equivalent to the 'git diff' option '-l'. 829 830diff.renames:: 831 Tells git to detect renames. If set to any boolean value, it 832 will enable basic rename detection. If set to "copies" or 833 "copy", it will detect copies, as well. 834 835diff.suppressBlankEmpty:: 836 A boolean to inhibit the standard behavior of printing a space 837 before each empty output line. Defaults to false. 838 839diff.tool:: 840 Controls which diff tool is used. `diff.tool` overrides 841 `merge.tool` when used by linkgit:git-difftool[1] and has 842 the same valid values as `merge.tool` minus "tortoisemerge" 843 and plus "kompare". 844 845difftool.<tool>.path:: 846 Override the path for the given tool. This is useful in case 847 your tool is not in the PATH. 848 849difftool.<tool>.cmd:: 850 Specify the command to invoke the specified diff tool. 851 The specified command is evaluated in shell with the following 852 variables available: 'LOCAL' is set to the name of the temporary 853 file containing the contents of the diff pre-image and 'REMOTE' 854 is set to the name of the temporary file containing the contents 855 of the diff post-image. 856 857difftool.prompt:: 858 Prompt before each invocation of the diff tool. 859 860diff.wordRegex:: 861 A POSIX Extended Regular Expression used to determine what is a "word" 862 when performing word-by-word difference calculations. Character 863 sequences that match the regular expression are "words", all other 864 characters are *ignorable* whitespace. 865 866fetch.unpackLimit:: 867 If the number of objects fetched over the git native 868 transfer is below this 869 limit, then the objects will be unpacked into loose object 870 files. However if the number of received objects equals or 871 exceeds this limit then the received pack will be stored as 872 a pack, after adding any missing delta bases. Storing the 873 pack from a push can make the push operation complete faster, 874 especially on slow filesystems. If not set, the value of 875 `transfer.unpackLimit` is used instead. 876 877format.attach:: 878 Enable multipart/mixed attachments as the default for 879 'format-patch'. The value can also be a double quoted string 880 which will enable attachments as the default and set the 881 value as the boundary. See the --attach option in 882 linkgit:git-format-patch[1]. 883 884format.numbered:: 885 A boolean which can enable or disable sequence numbers in patch 886 subjects. It defaults to "auto" which enables it only if there 887 is more than one patch. It can be enabled or disabled for all 888 messages by setting it to "true" or "false". See --numbered 889 option in linkgit:git-format-patch[1]. 890 891format.headers:: 892 Additional email headers to include in a patch to be submitted 893 by mail. See linkgit:git-format-patch[1]. 894 895format.to:: 896format.cc:: 897 Additional recipients to include in a patch to be submitted 898 by mail. See the --to and --cc options in 899 linkgit:git-format-patch[1]. 900 901format.subjectprefix:: 902 The default for format-patch is to output files with the '[PATCH]' 903 subject prefix. Use this variable to change that prefix. 904 905format.signature:: 906 The default for format-patch is to output a signature containing 907 the git version number. Use this variable to change that default. 908 Set this variable to the empty string ("") to suppress 909 signature generation. 910 911format.suffix:: 912 The default for format-patch is to output files with the suffix 913 `.patch`. Use this variable to change that suffix (make sure to 914 include the dot if you want it). 915 916format.pretty:: 917 The default pretty format for log/show/whatchanged command, 918 See linkgit:git-log[1], linkgit:git-show[1], 919 linkgit:git-whatchanged[1]. 920 921format.thread:: 922 The default threading style for 'git format-patch'. Can be 923 a boolean value, or `shallow` or `deep`. `shallow` threading 924 makes every mail a reply to the head of the series, 925 where the head is chosen from the cover letter, the 926 `\--in-reply-to`, and the first patch mail, in this order. 927 `deep` threading makes every mail a reply to the previous one. 928 A true boolean value is the same as `shallow`, and a false 929 value disables threading. 930 931format.signoff:: 932 A boolean value which lets you enable the `-s/--signoff` option of 933 format-patch by default. *Note:* Adding the Signed-off-by: line to a 934 patch should be a conscious act and means that you certify you have 935 the rights to submit this work under the same open source license. 936 Please see the 'SubmittingPatches' document for further discussion. 937 938gc.aggressiveWindow:: 939 The window size parameter used in the delta compression 940 algorithm used by 'git gc --aggressive'. This defaults 941 to 250. 942 943gc.auto:: 944 When there are approximately more than this many loose 945 objects in the repository, `git gc --auto` will pack them. 946 Some Porcelain commands use this command to perform a 947 light-weight garbage collection from time to time. The 948 default value is 6700. Setting this to 0 disables it. 949 950gc.autopacklimit:: 951 When there are more than this many packs that are not 952 marked with `*.keep` file in the repository, `git gc 953 --auto` consolidates them into one larger pack. The 954 default value is 50. Setting this to 0 disables it. 955 956gc.packrefs:: 957 Running `git pack-refs` in a repository renders it 958 unclonable by Git versions prior to 1.5.1.2 over dumb 959 transports such as HTTP. This variable determines whether 960 'git gc' runs `git pack-refs`. This can be set to `nobare` 961 to enable it within all non-bare repos or it can be set to a 962 boolean value. The default is `true`. 963 964gc.pruneexpire:: 965 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'. 966 Override the grace period with this config variable. The value 967 "now" may be used to disable this grace period and always prune 968 unreachable objects immediately. 969 970gc.reflogexpire:: 971gc.<pattern>.reflogexpire:: 972 'git reflog expire' removes reflog entries older than 973 this time; defaults to 90 days. With "<pattern>" (e.g. 974 "refs/stash") in the middle the setting applies only to 975 the refs that match the <pattern>. 976 977gc.reflogexpireunreachable:: 978gc.<ref>.reflogexpireunreachable:: 979 'git reflog expire' removes reflog entries older than 980 this time and are not reachable from the current tip; 981 defaults to 30 days. With "<pattern>" (e.g. "refs/stash") 982 in the middle, the setting applies only to the refs that 983 match the <pattern>. 984 985gc.rerereresolved:: 986 Records of conflicted merge you resolved earlier are 987 kept for this many days when 'git rerere gc' is run. 988 The default is 60 days. See linkgit:git-rerere[1]. 989 990gc.rerereunresolved:: 991 Records of conflicted merge you have not resolved are 992 kept for this many days when 'git rerere gc' is run. 993 The default is 15 days. See linkgit:git-rerere[1]. 994 995gitcvs.commitmsgannotation:: 996 Append this string to each commit message. Set to empty string 997 to disable this feature. Defaults to "via git-CVS emulator". 998 999gitcvs.enabled::1000 Whether the CVS server interface is enabled for this repository.1001 See linkgit:git-cvsserver[1].10021003gitcvs.logfile::1004 Path to a log file where the CVS server interface well... logs1005 various stuff. See linkgit:git-cvsserver[1].10061007gitcvs.usecrlfattr::1008 If true, the server will look up the end-of-line conversion1009 attributes for files to determine the '-k' modes to use. If1010 the attributes force git to treat a file as text,1011 the '-k' mode will be left blank so cvs clients will1012 treat it as text. If they suppress text conversion, the file1013 will be set with '-kb' mode, which suppresses any newline munging1014 the client might otherwise do. If the attributes do not allow1015 the file type to be determined, then 'gitcvs.allbinary' is1016 used. See linkgit:gitattributes[5].10171018gitcvs.allbinary::1019 This is used if 'gitcvs.usecrlfattr' does not resolve1020 the correct '-kb' mode to use. If true, all1021 unresolved files are sent to the client in1022 mode '-kb'. This causes the client to treat them1023 as binary files, which suppresses any newline munging it1024 otherwise might do. Alternatively, if it is set to "guess",1025 then the contents of the file are examined to decide if1026 it is binary, similar to 'core.autocrlf'.10271028gitcvs.dbname::1029 Database used by git-cvsserver to cache revision information1030 derived from the git repository. The exact meaning depends on the1031 used database driver, for SQLite (which is the default driver) this1032 is a filename. Supports variable substitution (see1033 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1034 Default: '%Ggitcvs.%m.sqlite'10351036gitcvs.dbdriver::1037 Used Perl DBI driver. You can specify any available driver1038 for this here, but it might not work. git-cvsserver is tested1039 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1040 reported *not* to work with 'DBD::mysql'. Experimental feature.1041 May not contain double colons (`:`). Default: 'SQLite'.1042 See linkgit:git-cvsserver[1].10431044gitcvs.dbuser, gitcvs.dbpass::1045 Database user and password. Only useful if setting 'gitcvs.dbdriver',1046 since SQLite has no concept of database users and/or passwords.1047 'gitcvs.dbuser' supports variable substitution (see1048 linkgit:git-cvsserver[1] for details).10491050gitcvs.dbTableNamePrefix::1051 Database table name prefix. Prepended to the names of any1052 database tables used, allowing a single database to be used1053 for several repositories. Supports variable substitution (see1054 linkgit:git-cvsserver[1] for details). Any non-alphabetic1055 characters will be replaced with underscores.10561057All gitcvs variables except for 'gitcvs.usecrlfattr' and1058'gitcvs.allbinary' can also be specified as1059'gitcvs.<access_method>.<varname>' (where 'access_method'1060is one of "ext" and "pserver") to make them apply only for the given1061access method.10621063gui.commitmsgwidth::1064 Defines how wide the commit message window is in the1065 linkgit:git-gui[1]. "75" is the default.10661067gui.diffcontext::1068 Specifies how many context lines should be used in calls to diff1069 made by the linkgit:git-gui[1]. The default is "5".10701071gui.encoding::1072 Specifies the default encoding to use for displaying of1073 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1074 It can be overridden by setting the 'encoding' attribute1075 for relevant files (see linkgit:gitattributes[5]).1076 If this option is not set, the tools default to the1077 locale encoding.10781079gui.matchtrackingbranch::1080 Determines if new branches created with linkgit:git-gui[1] should1081 default to tracking remote branches with matching names or1082 not. Default: "false".10831084gui.newbranchtemplate::1085 Is used as suggested name when creating new branches using the1086 linkgit:git-gui[1].10871088gui.pruneduringfetch::1089 "true" if linkgit:git-gui[1] should prune tracking branches when1090 performing a fetch. The default value is "false".10911092gui.trustmtime::1093 Determines if linkgit:git-gui[1] should trust the file modification1094 timestamp or not. By default the timestamps are not trusted.10951096gui.spellingdictionary::1097 Specifies the dictionary used for spell checking commit messages in1098 the linkgit:git-gui[1]. When set to "none" spell checking is turned1099 off.11001101gui.fastcopyblame::1102 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1103 location detection. It makes blame significantly faster on huge1104 repositories at the expense of less thorough copy detection.11051106gui.copyblamethreshold::1107 Specifies the threshold to use in 'git gui blame' original location1108 detection, measured in alphanumeric characters. See the1109 linkgit:git-blame[1] manual for more information on copy detection.11101111gui.blamehistoryctx::1112 Specifies the radius of history context in days to show in1113 linkgit:gitk[1] for the selected commit, when the `Show History1114 Context` menu item is invoked from 'git gui blame'. If this1115 variable is set to zero, the whole history is shown.11161117guitool.<name>.cmd::1118 Specifies the shell command line to execute when the corresponding item1119 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1120 mandatory for every tool. The command is executed from the root of1121 the working directory, and in the environment it receives the name of1122 the tool as 'GIT_GUITOOL', the name of the currently selected file as1123 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1124 the head is detached, 'CUR_BRANCH' is empty).11251126guitool.<name>.needsfile::1127 Run the tool only if a diff is selected in the GUI. It guarantees1128 that 'FILENAME' is not empty.11291130guitool.<name>.noconsole::1131 Run the command silently, without creating a window to display its1132 output.11331134guitool.<name>.norescan::1135 Don't rescan the working directory for changes after the tool1136 finishes execution.11371138guitool.<name>.confirm::1139 Show a confirmation dialog before actually running the tool.11401141guitool.<name>.argprompt::1142 Request a string argument from the user, and pass it to the tool1143 through the 'ARGS' environment variable. Since requesting an1144 argument implies confirmation, the 'confirm' option has no effect1145 if this is enabled. If the option is set to 'true', 'yes', or '1',1146 the dialog uses a built-in generic prompt; otherwise the exact1147 value of the variable is used.11481149guitool.<name>.revprompt::1150 Request a single valid revision from the user, and set the1151 'REVISION' environment variable. In other aspects this option1152 is similar to 'argprompt', and can be used together with it.11531154guitool.<name>.revunmerged::1155 Show only unmerged branches in the 'revprompt' subdialog.1156 This is useful for tools similar to merge or rebase, but not1157 for things like checkout or reset.11581159guitool.<name>.title::1160 Specifies the title to use for the prompt dialog. The default1161 is the tool name.11621163guitool.<name>.prompt::1164 Specifies the general prompt string to display at the top of1165 the dialog, before subsections for 'argprompt' and 'revprompt'.1166 The default value includes the actual command.11671168help.browser::1169 Specify the browser that will be used to display help in the1170 'web' format. See linkgit:git-help[1].11711172help.format::1173 Override the default help format used by linkgit:git-help[1].1174 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1175 the default. 'web' and 'html' are the same.11761177help.autocorrect::1178 Automatically correct and execute mistyped commands after1179 waiting for the given number of deciseconds (0.1 sec). If more1180 than one command can be deduced from the entered text, nothing1181 will be executed. If the value of this option is negative,1182 the corrected command will be executed immediately. If the1183 value is 0 - the command will be just shown but not executed.1184 This is the default.11851186http.proxy::1187 Override the HTTP proxy, normally configured using the 'http_proxy'1188 environment variable (see linkgit:curl[1]). This can be overridden1189 on a per-remote basis; see remote.<name>.proxy11901191http.sslVerify::1192 Whether to verify the SSL certificate when fetching or pushing1193 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1194 variable.11951196http.sslCert::1197 File containing the SSL certificate when fetching or pushing1198 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1199 variable.12001201http.sslKey::1202 File containing the SSL private key when fetching or pushing1203 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1204 variable.12051206http.sslCertPasswordProtected::1207 Enable git's password prompt for the SSL certificate. Otherwise1208 OpenSSL will prompt the user, possibly many times, if the1209 certificate or private key is encrypted. Can be overridden by the1210 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.12111212http.sslCAInfo::1213 File containing the certificates to verify the peer with when1214 fetching or pushing over HTTPS. Can be overridden by the1215 'GIT_SSL_CAINFO' environment variable.12161217http.sslCAPath::1218 Path containing files with the CA certificates to verify the peer1219 with when fetching or pushing over HTTPS. Can be overridden1220 by the 'GIT_SSL_CAPATH' environment variable.12211222http.maxRequests::1223 How many HTTP requests to launch in parallel. Can be overridden1224 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.12251226http.minSessions::1227 The number of curl sessions (counted across slots) to be kept across1228 requests. They will not be ended with curl_easy_cleanup() until1229 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1230 value will be capped at 1. Defaults to 1.12311232http.postBuffer::1233 Maximum size in bytes of the buffer used by smart HTTP1234 transports when POSTing data to the remote system.1235 For requests larger than this buffer size, HTTP/1.1 and1236 Transfer-Encoding: chunked is used to avoid creating a1237 massive pack file locally. Default is 1 MiB, which is1238 sufficient for most requests.12391240http.lowSpeedLimit, http.lowSpeedTime::1241 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1242 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1243 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1244 'GIT_HTTP_LOW_SPEED_TIME' environment variables.12451246http.noEPSV::1247 A boolean which disables using of EPSV ftp command by curl.1248 This can helpful with some "poor" ftp servers which don't1249 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1250 environment variable. Default is false (curl will use EPSV).12511252i18n.commitEncoding::1253 Character encoding the commit messages are stored in; git itself1254 does not care per se, but this information is necessary e.g. when1255 importing commits from emails or in the gitk graphical history1256 browser (and possibly at other places in the future or in other1257 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.12581259i18n.logOutputEncoding::1260 Character encoding the commit messages are converted to when1261 running 'git log' and friends.12621263imap::1264 The configuration variables in the 'imap' section are described1265 in linkgit:git-imap-send[1].12661267init.templatedir::1268 Specify the directory from which templates will be copied.1269 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)12701271instaweb.browser::1272 Specify the program that will be used to browse your working1273 repository in gitweb. See linkgit:git-instaweb[1].12741275instaweb.httpd::1276 The HTTP daemon command-line to start gitweb on your working1277 repository. See linkgit:git-instaweb[1].12781279instaweb.local::1280 If true the web server started by linkgit:git-instaweb[1] will1281 be bound to the local IP (127.0.0.1).12821283instaweb.modulepath::1284 The module path for an apache httpd used by linkgit:git-instaweb[1].12851286instaweb.port::1287 The port number to bind the gitweb httpd to. See1288 linkgit:git-instaweb[1].12891290interactive.singlekey::1291 In interactive commands, allow the user to provide one-letter1292 input with a single key (i.e., without hitting enter).1293 Currently this is used only by the `\--patch` mode of1294 linkgit:git-add[1]. Note that this setting is silently1295 ignored if portable keystroke input is not available.12961297log.date::1298 Set default date-time mode for the log command. Setting log.date1299 value is similar to using 'git log'\'s --date option. The value is one of the1300 following alternatives: {relative,local,default,iso,rfc,short}.1301 See linkgit:git-log[1].13021303log.decorate::1304 Print out the ref names of any commits that are shown by the log1305 command. If 'short' is specified, the ref name prefixes 'refs/heads/',1306 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is1307 specified, the full ref name (including prefix) will be printed.1308 This is the same as the log commands '--decorate' option.13091310log.showroot::1311 If true, the initial commit will be shown as a big creation event.1312 This is equivalent to a diff against an empty tree.1313 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1314 normally hide the root commit will now show it. True by default.13151316mailmap.file::1317 The location of an augmenting mailmap file. The default1318 mailmap, located in the root of the repository, is loaded1319 first, then the mailmap file pointed to by this variable.1320 The location of the mailmap file may be in a repository1321 subdirectory, or somewhere outside of the repository itself.1322 See linkgit:git-shortlog[1] and linkgit:git-blame[1].13231324man.viewer::1325 Specify the programs that may be used to display help in the1326 'man' format. See linkgit:git-help[1].13271328man.<tool>.cmd::1329 Specify the command to invoke the specified man viewer. The1330 specified command is evaluated in shell with the man page1331 passed as argument. (See linkgit:git-help[1].)13321333man.<tool>.path::1334 Override the path for the given tool that may be used to1335 display help in the 'man' format. See linkgit:git-help[1].13361337include::merge-config.txt[]13381339mergetool.<tool>.path::1340 Override the path for the given tool. This is useful in case1341 your tool is not in the PATH.13421343mergetool.<tool>.cmd::1344 Specify the command to invoke the specified merge tool. The1345 specified command is evaluated in shell with the following1346 variables available: 'BASE' is the name of a temporary file1347 containing the common base of the files to be merged, if available;1348 'LOCAL' is the name of a temporary file containing the contents of1349 the file on the current branch; 'REMOTE' is the name of a temporary1350 file containing the contents of the file from the branch being1351 merged; 'MERGED' contains the name of the file to which the merge1352 tool should write the results of a successful merge.13531354mergetool.<tool>.trustExitCode::1355 For a custom merge command, specify whether the exit code of1356 the merge command can be used to determine whether the merge was1357 successful. If this is not set to true then the merge target file1358 timestamp is checked and the merge assumed to have been successful1359 if the file has been updated, otherwise the user is prompted to1360 indicate the success of the merge.13611362mergetool.keepBackup::1363 After performing a merge, the original file with conflict markers1364 can be saved as a file with a `.orig` extension. If this variable1365 is set to `false` then this file is not preserved. Defaults to1366 `true` (i.e. keep the backup files).13671368mergetool.keepTemporaries::1369 When invoking a custom merge tool, git uses a set of temporary1370 files to pass to the tool. If the tool returns an error and this1371 variable is set to `true`, then these temporary files will be1372 preserved, otherwise they will be removed after the tool has1373 exited. Defaults to `false`.13741375mergetool.prompt::1376 Prompt before each invocation of the merge resolution program.13771378notes.displayRef::1379 The (fully qualified) refname from which to show notes when1380 showing commit messages. The value of this variable can be set1381 to a glob, in which case notes from all matching refs will be1382 shown. You may also specify this configuration variable1383 several times. A warning will be issued for refs that do not1384 exist, but a glob that does not match any refs is silently1385 ignored.1386+1387This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`1388environment variable, which must be a colon separated list of refs or1389globs.1390+1391The effective value of "core.notesRef" (possibly overridden by1392GIT_NOTES_REF) is also implicitly added to the list of refs to be1393displayed.13941395notes.rewrite.<command>::1396 When rewriting commits with <command> (currently `amend` or1397 `rebase`) and this variable is set to `true`, git1398 automatically copies your notes from the original to the1399 rewritten commit. Defaults to `true`, but see1400 "notes.rewriteRef" below.14011402notes.rewriteMode::1403 When copying notes during a rewrite (see the1404 "notes.rewrite.<command>" option), determines what to do if1405 the target commit already has a note. Must be one of1406 `overwrite`, `concatenate`, or `ignore`. Defaults to1407 `concatenate`.1408+1409This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`1410environment variable.14111412notes.rewriteRef::1413 When copying notes during a rewrite, specifies the (fully1414 qualified) ref whose notes should be copied. The ref may be a1415 glob, in which case notes in all matching refs will be copied.1416 You may also specify this configuration several times.1417+1418Does not have a default value; you must configure this variable to1419enable note rewriting.1420+1421This setting can be overridden with the `GIT_NOTES_REWRITE_REF`1422environment variable, which must be a colon separated list of refs or1423globs.14241425pack.window::1426 The size of the window used by linkgit:git-pack-objects[1] when no1427 window size is given on the command line. Defaults to 10.14281429pack.depth::1430 The maximum delta depth used by linkgit:git-pack-objects[1] when no1431 maximum depth is given on the command line. Defaults to 50.14321433pack.windowMemory::1434 The window memory size limit used by linkgit:git-pack-objects[1]1435 when no limit is given on the command line. The value can be1436 suffixed with "k", "m", or "g". Defaults to 0, meaning no1437 limit.14381439pack.compression::1440 An integer -1..9, indicating the compression level for objects1441 in a pack file. -1 is the zlib default. 0 means no1442 compression, and 1..9 are various speed/size tradeoffs, 9 being1443 slowest. If not set, defaults to core.compression. If that is1444 not set, defaults to -1, the zlib default, which is "a default1445 compromise between speed and compression (currently equivalent1446 to level 6)."14471448pack.deltaCacheSize::1449 The maximum memory in bytes used for caching deltas in1450 linkgit:git-pack-objects[1] before writing them out to a pack.1451 This cache is used to speed up the writing object phase by not1452 having to recompute the final delta result once the best match1453 for all objects is found. Repacking large repositories on machines1454 which are tight with memory might be badly impacted by this though,1455 especially if this cache pushes the system into swapping.1456 A value of 0 means no limit. The smallest size of 1 byte may be1457 used to virtually disable this cache. Defaults to 256 MiB.14581459pack.deltaCacheLimit::1460 The maximum size of a delta, that is cached in1461 linkgit:git-pack-objects[1]. This cache is used to speed up the1462 writing object phase by not having to recompute the final delta1463 result once the best match for all objects is found. Defaults to 1000.14641465pack.threads::1466 Specifies the number of threads to spawn when searching for best1467 delta matches. This requires that linkgit:git-pack-objects[1]1468 be compiled with pthreads otherwise this option is ignored with a1469 warning. This is meant to reduce packing time on multiprocessor1470 machines. The required amount of memory for the delta search window1471 is however multiplied by the number of threads.1472 Specifying 0 will cause git to auto-detect the number of CPU's1473 and set the number of threads accordingly.14741475pack.indexVersion::1476 Specify the default pack index version. Valid values are 1 for1477 legacy pack index used by Git versions prior to 1.5.2, and 2 for1478 the new pack index with capabilities for packs larger than 4 GB1479 as well as proper protection against the repacking of corrupted1480 packs. Version 2 is the default. Note that version 2 is enforced1481 and this config option ignored whenever the corresponding pack is1482 larger than 2 GB.1483+1484If you have an old git that does not understand the version 2 `{asterisk}.idx` file,1485cloning or fetching over a non native protocol (e.g. "http" and "rsync")1486that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the1487other side may give you a repository that cannot be accessed with your1488older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,1489you can use linkgit:git-index-pack[1] on the *.pack file to regenerate1490the `{asterisk}.idx` file.14911492pack.packSizeLimit::1493 The maximum size of a pack. This setting only affects1494 packing to a file when repacking, i.e. the git:// protocol1495 is unaffected. It can be overridden by the `\--max-pack-size`1496 option of linkgit:git-repack[1]. The minimum size allowed is1497 limited to 1 MiB. The default is unlimited.1498 Common unit suffixes of 'k', 'm', or 'g' are1499 supported.15001501pager.<cmd>::1502 Allows turning on or off pagination of the output of a1503 particular git subcommand when writing to a tty. If1504 `\--paginate` or `\--no-pager` is specified on the command line,1505 it takes precedence over this option. To disable pagination for1506 all commands, set `core.pager` or `GIT_PAGER` to `cat`.15071508pretty.<name>::1509 Alias for a --pretty= format string, as specified in1510 linkgit:git-log[1]. Any aliases defined here can be used just1511 as the built-in pretty formats could. For example,1512 running `git config pretty.changelog "format:{asterisk} %H %s"`1513 would cause the invocation `git log --pretty=changelog`1514 to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.1515 Note that an alias with the same name as a built-in format1516 will be silently ignored.15171518pull.octopus::1519 The default merge strategy to use when pulling multiple branches1520 at once.15211522pull.twohead::1523 The default merge strategy to use when pulling a single branch.15241525push.default::1526 Defines the action git push should take if no refspec is given1527 on the command line, no refspec is configured in the remote, and1528 no refspec is implied by any of the options given on the command1529 line. Possible values are:1530+1531* `nothing` do not push anything.1532* `matching` push all matching branches.1533 All branches having the same name in both ends are considered to be1534 matching. This is the default.1535* `tracking` push the current branch to its upstream branch.1536* `current` push the current branch to a branch of the same name.15371538rebase.stat::1539 Whether to show a diffstat of what changed upstream since the last1540 rebase. False by default.15411542receive.autogc::1543 By default, git-receive-pack will run "git-gc --auto" after1544 receiving data from git-push and updating refs. You can stop1545 it by setting this variable to false.15461547receive.fsckObjects::1548 If it is set to true, git-receive-pack will check all received1549 objects. It will abort in the case of a malformed object or a1550 broken link. The result of an abort are only dangling objects.1551 Defaults to false.15521553receive.unpackLimit::1554 If the number of objects received in a push is below this1555 limit then the objects will be unpacked into loose object1556 files. However if the number of received objects equals or1557 exceeds this limit then the received pack will be stored as1558 a pack, after adding any missing delta bases. Storing the1559 pack from a push can make the push operation complete faster,1560 especially on slow filesystems. If not set, the value of1561 `transfer.unpackLimit` is used instead.15621563receive.denyDeletes::1564 If set to true, git-receive-pack will deny a ref update that deletes1565 the ref. Use this to prevent such a ref deletion via a push.15661567receive.denyCurrentBranch::1568 If set to true or "refuse", git-receive-pack will deny a ref update1569 to the currently checked out branch of a non-bare repository.1570 Such a push is potentially dangerous because it brings the HEAD1571 out of sync with the index and working tree. If set to "warn",1572 print a warning of such a push to stderr, but allow the push to1573 proceed. If set to false or "ignore", allow such pushes with no1574 message. Defaults to "refuse".15751576receive.denyNonFastForwards::1577 If set to true, git-receive-pack will deny a ref update which is1578 not a fast-forward. Use this to prevent such an update via a push,1579 even if that push is forced. This configuration variable is1580 set when initializing a shared repository.15811582receive.updateserverinfo::1583 If set to true, git-receive-pack will run git-update-server-info1584 after receiving data from git-push and updating refs.15851586remote.<name>.url::1587 The URL of a remote repository. See linkgit:git-fetch[1] or1588 linkgit:git-push[1].15891590remote.<name>.pushurl::1591 The push URL of a remote repository. See linkgit:git-push[1].15921593remote.<name>.proxy::1594 For remotes that require curl (http, https and ftp), the URL to1595 the proxy to use for that remote. Set to the empty string to1596 disable proxying for that remote.15971598remote.<name>.fetch::1599 The default set of "refspec" for linkgit:git-fetch[1]. See1600 linkgit:git-fetch[1].16011602remote.<name>.push::1603 The default set of "refspec" for linkgit:git-push[1]. See1604 linkgit:git-push[1].16051606remote.<name>.mirror::1607 If true, pushing to this remote will automatically behave1608 as if the `\--mirror` option was given on the command line.16091610remote.<name>.skipDefaultUpdate::1611 If true, this remote will be skipped by default when updating1612 using linkgit:git-fetch[1] or the `update` subcommand of1613 linkgit:git-remote[1].16141615remote.<name>.skipFetchAll::1616 If true, this remote will be skipped by default when updating1617 using linkgit:git-fetch[1] or the `update` subcommand of1618 linkgit:git-remote[1].16191620remote.<name>.receivepack::1621 The default program to execute on the remote side when pushing. See1622 option \--receive-pack of linkgit:git-push[1].16231624remote.<name>.uploadpack::1625 The default program to execute on the remote side when fetching. See1626 option \--upload-pack of linkgit:git-fetch-pack[1].16271628remote.<name>.tagopt::1629 Setting this value to \--no-tags disables automatic tag following when1630 fetching from remote <name>. Setting it to \--tags will fetch every1631 tag from remote <name>, even if they are not reachable from remote1632 branch heads.16331634remote.<name>.vcs::1635 Setting this to a value <vcs> will cause git to interact with1636 the remote with the git-remote-<vcs> helper.16371638remotes.<group>::1639 The list of remotes which are fetched by "git remote update1640 <group>". See linkgit:git-remote[1].16411642repack.usedeltabaseoffset::1643 By default, linkgit:git-repack[1] creates packs that use1644 delta-base offset. If you need to share your repository with1645 git older than version 1.4.4, either directly or via a dumb1646 protocol such as http, then you need to set this option to1647 "false" and repack. Access from old git versions over the1648 native protocol are unaffected by this option.16491650rerere.autoupdate::1651 When set to true, `git-rerere` updates the index with the1652 resulting contents after it cleanly resolves conflicts using1653 previously recorded resolution. Defaults to false.16541655rerere.enabled::1656 Activate recording of resolved conflicts, so that identical1657 conflict hunks can be resolved automatically, should they1658 be encountered again. linkgit:git-rerere[1] command is by1659 default enabled if you create `rr-cache` directory under1660 `$GIT_DIR`, but can be disabled by setting this option to false.16611662sendemail.identity::1663 A configuration identity. When given, causes values in the1664 'sendemail.<identity>' subsection to take precedence over1665 values in the 'sendemail' section. The default identity is1666 the value of 'sendemail.identity'.16671668sendemail.smtpencryption::1669 See linkgit:git-send-email[1] for description. Note that this1670 setting is not subject to the 'identity' mechanism.16711672sendemail.smtpssl::1673 Deprecated alias for 'sendemail.smtpencryption = ssl'.16741675sendemail.<identity>.*::1676 Identity-specific versions of the 'sendemail.*' parameters1677 found below, taking precedence over those when the this1678 identity is selected, through command-line or1679 'sendemail.identity'.16801681sendemail.aliasesfile::1682sendemail.aliasfiletype::1683sendemail.bcc::1684sendemail.cc::1685sendemail.cccmd::1686sendemail.chainreplyto::1687sendemail.confirm::1688sendemail.envelopesender::1689sendemail.from::1690sendemail.multiedit::1691sendemail.signedoffbycc::1692sendemail.smtppass::1693sendemail.suppresscc::1694sendemail.suppressfrom::1695sendemail.to::1696sendemail.smtpdomain::1697sendemail.smtpserver::1698sendemail.smtpserverport::1699sendemail.smtpuser::1700sendemail.thread::1701sendemail.validate::1702 See linkgit:git-send-email[1] for description.17031704sendemail.signedoffcc::1705 Deprecated alias for 'sendemail.signedoffbycc'.17061707showbranch.default::1708 The default set of branches for linkgit:git-show-branch[1].1709 See linkgit:git-show-branch[1].17101711status.relativePaths::1712 By default, linkgit:git-status[1] shows paths relative to the1713 current directory. Setting this variable to `false` shows paths1714 relative to the repository root (this was the default for git1715 prior to v1.5.4).17161717status.showUntrackedFiles::1718 By default, linkgit:git-status[1] and linkgit:git-commit[1] show1719 files which are not currently tracked by Git. Directories which1720 contain only untracked files, are shown with the directory name1721 only. Showing untracked files means that Git needs to lstat() all1722 all the files in the whole repository, which might be slow on some1723 systems. So, this variable controls how the commands displays1724 the untracked files. Possible values are:1725+1726--1727 - 'no' - Show no untracked files1728 - 'normal' - Shows untracked files and directories1729 - 'all' - Shows also individual files in untracked directories.1730--1731+1732If this variable is not specified, it defaults to 'normal'.1733This variable can be overridden with the -u|--untracked-files option1734of linkgit:git-status[1] and linkgit:git-commit[1].17351736status.submodulesummary::1737 Defaults to false.1738 If this is set to a non zero number or true (identical to -1 or an1739 unlimited number), the submodule summary will be enabled and a1740 summary of commits for modified submodules will be shown (see1741 --summary-limit option of linkgit:git-submodule[1]).17421743submodule.<name>.path::1744submodule.<name>.url::1745submodule.<name>.update::1746 The path within this project, URL, and the updating strategy1747 for a submodule. These variables are initially populated1748 by 'git submodule init'; edit them to override the1749 URL and other values found in the `.gitmodules` file. See1750 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.17511752tar.umask::1753 This variable can be used to restrict the permission bits of1754 tar archive entries. The default is 0002, which turns off the1755 world write bit. The special value "user" indicates that the1756 archiving user's umask will be used instead. See umask(2) and1757 linkgit:git-archive[1].17581759transfer.unpackLimit::1760 When `fetch.unpackLimit` or `receive.unpackLimit` are1761 not set, the value of this variable is used instead.1762 The default value is 100.17631764url.<base>.insteadOf::1765 Any URL that starts with this value will be rewritten to1766 start, instead, with <base>. In cases where some site serves a1767 large number of repositories, and serves them with multiple1768 access methods, and some users need to use different access1769 methods, this feature allows people to specify any of the1770 equivalent URLs and have git automatically rewrite the URL to1771 the best alternative for the particular user, even for a1772 never-before-seen repository on the site. When more than one1773 insteadOf strings match a given URL, the longest match is used.17741775url.<base>.pushInsteadOf::1776 Any URL that starts with this value will not be pushed to;1777 instead, it will be rewritten to start with <base>, and the1778 resulting URL will be pushed to. In cases where some site serves1779 a large number of repositories, and serves them with multiple1780 access methods, some of which do not allow push, this feature1781 allows people to specify a pull-only URL and have git1782 automatically use an appropriate URL to push, even for a1783 never-before-seen repository on the site. When more than one1784 pushInsteadOf strings match a given URL, the longest match is1785 used. If a remote has an explicit pushurl, git will ignore this1786 setting for that remote.17871788user.email::1789 Your email address to be recorded in any newly created commits.1790 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and1791 'EMAIL' environment variables. See linkgit:git-commit-tree[1].17921793user.name::1794 Your full name to be recorded in any newly created commits.1795 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'1796 environment variables. See linkgit:git-commit-tree[1].17971798user.signingkey::1799 If linkgit:git-tag[1] is not selecting the key you want it to1800 automatically when creating a signed tag, you can override the1801 default selection with this variable. This option is passed1802 unchanged to gpg's --local-user parameter, so you may specify a key1803 using any method that gpg supports.18041805web.browser::1806 Specify a web browser that may be used by some commands.1807 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]1808 may use it.