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, allow only alphanumeric 16characters and `-`, and must start with an alphabetic character. Some 17variables may appear multiple times. 18 19Syntax 20~~~~~~ 21 22The syntax is fairly flexible and permissive; whitespaces are mostly 23ignored. The '#' and ';' characters begin comments to the end of line, 24blank lines are ignored. 25 26The file consists of sections and variables. A section begins with 27the name of the section in square brackets and continues until the next 28section begins. Section names are not case sensitive. Only alphanumeric 29characters, `-` and `.` are allowed in section names. Each variable 30must belong to some section, which means that there must be a section 31header before the first setting of a variable. 32 33Sections can be further divided into subsections. To begin a subsection 34put its name in double quotes, separated by space from the section name, 35in the section header, like in the example below: 36 37-------- 38 [section "subsection"] 39 40-------- 41 42Subsection names are case sensitive and can contain any characters except 43newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`, 44respectively). Section headers cannot span multiple 45lines. Variables may belong directly to a section or to a given subsection. 46You can have `[section]` if you have `[section "subsection"]`, but you 47don't need to. 48 49There is also a deprecated `[section.subsection]` syntax. With this 50syntax, the subsection name is converted to lower-case and is also 51compared case sensitively. These subsection names follow the same 52restrictions as section names. 53 54All the other lines (and the remainder of the line after the section 55header) are recognized as setting variables, in the form 56'name = value'. If there is no equal sign on the line, the entire line 57is taken as 'name' and the variable is recognized as boolean "true". 58The variable names are case-insensitive, allow only alphanumeric characters 59and `-`, and must start with an alphabetic character. There can be more 60than one value for a given variable; we say then that the variable is 61multivalued. 62 63Leading and trailing whitespace in a variable value is discarded. 64Internal whitespace within a variable value is retained verbatim. 65 66The values following the equals sign in variable assign are all either 67a string, an integer, or a boolean. Boolean values may be given as yes/no, 681/0, true/false or on/off. Case is not significant in boolean values, when 69converting value to the canonical form using '--bool' type specifier; 70'git config' will ensure that the output is "true" or "false". 71 72String values may be entirely or partially enclosed in double quotes. 73You need to enclose variable values in double quotes if you want to 74preserve leading or trailing whitespace, or if the variable value contains 75comment characters (i.e. it contains '#' or ';'). 76Double quote `"` and backslash `\` characters in variable values must 77be escaped: use `\"` for `"` and `\\` for `\`. 78 79The following escape sequences (beside `\"` and `\\`) are recognized: 80`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) 81and `\b` for backspace (BS). No other char escape sequence, nor octal 82char sequences are valid. 83 84Variable values ending in a `\` are continued on the next line in the 85customary UNIX fashion. 86 87Some variables may require a special value format. 88 89Includes 90~~~~~~~~ 91 92You can include one config file from another by setting the special 93`include.path` variable to the name of the file to be included. The 94included file is expanded immediately, as if its contents had been 95found at the location of the include directive. If the value of the 96`include.path` variable is a relative path, the path is considered to be 97relative to the configuration file in which the include directive was 98found. The value of `include.path` is subject to tilde expansion: `{tilde}/` 99is expanded to the value of `$HOME`, and `{tilde}user/` to the specified 100user's home directory. See below for examples. 101 102Example 103~~~~~~~ 104 105 # Core variables 106 [core] 107 ; Don't trust file modes 108 filemode = false 109 110 # Our diff algorithm 111 [diff] 112 external = /usr/local/bin/diff-wrapper 113 renames = true 114 115 [branch "devel"] 116 remote = origin 117 merge = refs/heads/devel 118 119 # Proxy settings 120 [core] 121 gitProxy="ssh" for "kernel.org" 122 gitProxy=default-proxy ; for the rest 123 124 [include] 125 path = /path/to/foo.inc ; include by absolute path 126 path = foo ; expand "foo" relative to the current file 127 path = ~/foo ; expand "foo" in your $HOME directory 128 129Variables 130~~~~~~~~~ 131 132Note that this list is non-comprehensive and not necessarily complete. 133For command-specific variables, you will find a more detailed description 134in the appropriate manual page. You will find a description of non-core 135porcelain configuration variables in the respective porcelain documentation. 136 137advice.*:: 138 These variables control various optional help messages designed to 139 aid new users. All 'advice.*' variables default to 'true', and you 140 can tell Git that you do not need help by setting these to 'false': 141+ 142-- 143 pushNonFastForward:: 144 Advice shown when linkgit:git-push[1] refuses 145 non-fast-forward refs. 146 statusHints:: 147 Directions on how to stage/unstage/add shown in the 148 output of linkgit:git-status[1] and the template shown 149 when writing commit messages. 150 commitBeforeMerge:: 151 Advice shown when linkgit:git-merge[1] refuses to 152 merge to avoid overwriting local changes. 153 resolveConflict:: 154 Advices shown by various commands when conflicts 155 prevent the operation from being performed. 156 implicitIdentity:: 157 Advice on how to set your identity configuration when 158 your information is guessed from the system username and 159 domain name. 160 detachedHead:: 161 Advice shown when you used linkgit:git-checkout[1] to 162 move to the detach HEAD state, to instruct how to create 163 a local branch after the fact. 164-- 165 166core.fileMode:: 167 If false, the executable bit differences between the index and 168 the working tree are ignored; useful on broken filesystems like FAT. 169 See linkgit:git-update-index[1]. 170+ 171The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 172will probe and set core.fileMode false if appropriate when the 173repository is created. 174 175core.ignoreCygwinFSTricks:: 176 This option is only used by Cygwin implementation of Git. If false, 177 the Cygwin stat() and lstat() functions are used. This may be useful 178 if your repository consists of a few separate directories joined in 179 one hierarchy using Cygwin mount. If true, Git uses native Win32 API 180 whenever it is possible and falls back to Cygwin functions only to 181 handle symbol links. The native mode is more than twice faster than 182 normal Cygwin l/stat() functions. True by default, unless core.filemode 183 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's 184 POSIX emulation is required to support core.filemode. 185 186core.ignorecase:: 187 If true, this option enables various workarounds to enable 188 git to work better on filesystems that are not case sensitive, 189 like FAT. For example, if a directory listing finds 190 "makefile" when git expects "Makefile", git will assume 191 it is really the same file, and continue to remember it as 192 "Makefile". 193+ 194The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 195will probe and set core.ignorecase true if appropriate when the repository 196is created. 197 198core.trustctime:: 199 If false, the ctime differences between the index and the 200 working tree are ignored; useful when the inode change time 201 is regularly modified by something outside Git (file system 202 crawlers and some backup systems). 203 See linkgit:git-update-index[1]. True by default. 204 205core.quotepath:: 206 The commands that output paths (e.g. 'ls-files', 207 'diff'), when not given the `-z` option, will quote 208 "unusual" characters in the pathname by enclosing the 209 pathname in a double-quote pair and with backslashes the 210 same way strings in C source code are quoted. If this 211 variable is set to false, the bytes higher than 0x80 are 212 not quoted but output as verbatim. Note that double 213 quote, backslash and control characters are always 214 quoted without `-z` regardless of the setting of this 215 variable. 216 217core.eol:: 218 Sets the line ending type to use in the working directory for 219 files that have the `text` property set. Alternatives are 220 'lf', 'crlf' and 'native', which uses the platform's native 221 line ending. The default value is `native`. See 222 linkgit:gitattributes[5] for more information on end-of-line 223 conversion. 224 225core.safecrlf:: 226 If true, makes git check if converting `CRLF` is reversible when 227 end-of-line conversion is active. Git will verify if a command 228 modifies a file in the work tree either directly or indirectly. 229 For example, committing a file followed by checking out the 230 same file should yield the original file in the work tree. If 231 this is not the case for the current setting of 232 `core.autocrlf`, git will reject the file. The variable can 233 be set to "warn", in which case git will only warn about an 234 irreversible conversion but continue the operation. 235+ 236CRLF conversion bears a slight chance of corrupting data. 237When it is enabled, git will convert CRLF to LF during commit and LF to 238CRLF during checkout. A file that contains a mixture of LF and 239CRLF before the commit cannot be recreated by git. For text 240files this is the right thing to do: it corrects line endings 241such that we have only LF line endings in the repository. 242But for binary files that are accidentally classified as text the 243conversion can corrupt data. 244+ 245If you recognize such corruption early you can easily fix it by 246setting the conversion type explicitly in .gitattributes. Right 247after committing you still have the original file in your work 248tree and this file is not yet corrupted. You can explicitly tell 249git that this file is binary and git will handle the file 250appropriately. 251+ 252Unfortunately, the desired effect of cleaning up text files with 253mixed line endings and the undesired effect of corrupting binary 254files cannot be distinguished. In both cases CRLFs are removed 255in an irreversible way. For text files this is the right thing 256to do because CRLFs are line endings, while for binary files 257converting CRLFs corrupts data. 258+ 259Note, this safety check does not mean that a checkout will generate a 260file identical to the original file for a different setting of 261`core.eol` and `core.autocrlf`, but only for the current one. For 262example, a text file with `LF` would be accepted with `core.eol=lf` 263and could later be checked out with `core.eol=crlf`, in which case the 264resulting file would contain `CRLF`, although the original file 265contained `LF`. However, in both work trees the line endings would be 266consistent, that is either all `LF` or all `CRLF`, but never mixed. A 267file with mixed line endings would be reported by the `core.safecrlf` 268mechanism. 269 270core.autocrlf:: 271 Setting this variable to "true" is almost the same as setting 272 the `text` attribute to "auto" on all files except that text 273 files are not guaranteed to be normalized: files that contain 274 `CRLF` in the repository will not be touched. Use this 275 setting if you want to have `CRLF` line endings in your 276 working directory even though the repository does not have 277 normalized line endings. This variable can be set to 'input', 278 in which case no output conversion is performed. 279 280core.symlinks:: 281 If false, symbolic links are checked out as small plain files that 282 contain the link text. linkgit:git-update-index[1] and 283 linkgit:git-add[1] will not change the recorded type to regular 284 file. Useful on filesystems like FAT that do not support 285 symbolic links. 286+ 287The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 288will probe and set core.symlinks false if appropriate when the repository 289is created. 290 291core.gitProxy:: 292 A "proxy command" to execute (as 'command host port') instead 293 of establishing direct connection to the remote server when 294 using the git protocol for fetching. If the variable value is 295 in the "COMMAND for DOMAIN" format, the command is applied only 296 on hostnames ending with the specified domain string. This variable 297 may be set multiple times and is matched in the given order; 298 the first match wins. 299+ 300Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 301(which always applies universally, without the special "for" 302handling). 303+ 304The special string `none` can be used as the proxy command to 305specify that no proxy be used for a given domain pattern. 306This is useful for excluding servers inside a firewall from 307proxy use, while defaulting to a common proxy for external domains. 308 309core.ignoreStat:: 310 If true, commands which modify both the working tree and the index 311 will mark the updated paths with the "assume unchanged" bit in the 312 index. These marked files are then assumed to stay unchanged in the 313 working tree, until you mark them otherwise manually - Git will not 314 detect the file changes by lstat() calls. This is useful on systems 315 where those are very slow, such as Microsoft Windows. 316 See linkgit:git-update-index[1]. 317 False by default. 318 319core.preferSymlinkRefs:: 320 Instead of the default "symref" format for HEAD 321 and other symbolic reference files, use symbolic links. 322 This is sometimes needed to work with old scripts that 323 expect HEAD to be a symbolic link. 324 325core.bare:: 326 If true this repository is assumed to be 'bare' and has no 327 working directory associated with it. If this is the case a 328 number of commands that require a working directory will be 329 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 330+ 331This setting is automatically guessed by linkgit:git-clone[1] or 332linkgit:git-init[1] when the repository was created. By default a 333repository that ends in "/.git" is assumed to be not bare (bare = 334false), while all other repositories are assumed to be bare (bare 335= true). 336 337core.worktree:: 338 Set the path to the root of the working tree. 339 This can be overridden by the GIT_WORK_TREE environment 340 variable and the '--work-tree' command line option. 341 The value can be an absolute path or relative to the path to 342 the .git directory, which is either specified by --git-dir 343 or GIT_DIR, or automatically discovered. 344 If --git-dir or GIT_DIR is specified but none of 345 --work-tree, GIT_WORK_TREE and core.worktree is specified, 346 the current working directory is regarded as the top level 347 of your working tree. 348+ 349Note that this variable is honored even when set in a configuration 350file in a ".git" subdirectory of a directory and its value differs 351from the latter directory (e.g. "/path/to/.git/config" has 352core.worktree set to "/different/path"), which is most likely a 353misconfiguration. Running git commands in the "/path/to" directory will 354still use "/different/path" as the root of the work tree and can cause 355confusion unless you know what you are doing (e.g. you are creating a 356read-only snapshot of the same index to a location different from the 357repository's usual working tree). 358 359core.logAllRefUpdates:: 360 Enable the reflog. Updates to a ref <ref> is logged to the file 361 "$GIT_DIR/logs/<ref>", by appending the new and old 362 SHA1, the date/time and the reason of the update, but 363 only when the file exists. If this configuration 364 variable is set to true, missing "$GIT_DIR/logs/<ref>" 365 file is automatically created for branch heads (i.e. under 366 refs/heads/), remote refs (i.e. under refs/remotes/), 367 note refs (i.e. under refs/notes/), and the symbolic ref HEAD. 368+ 369This information can be used to determine what commit 370was the tip of a branch "2 days ago". 371+ 372This value is true by default in a repository that has 373a working directory associated with it, and false by 374default in a bare repository. 375 376core.repositoryFormatVersion:: 377 Internal variable identifying the repository format and layout 378 version. 379 380core.sharedRepository:: 381 When 'group' (or 'true'), the repository is made shareable between 382 several users in a group (making sure all the files and objects are 383 group-writable). When 'all' (or 'world' or 'everybody'), the 384 repository will be readable by all users, additionally to being 385 group-shareable. When 'umask' (or 'false'), git will use permissions 386 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 387 files in the repository will have this mode value. '0xxx' will override 388 user's umask value (whereas the other options will only override 389 requested parts of the user's umask value). Examples: '0660' will make 390 the repo read/write-able for the owner and group, but inaccessible to 391 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 392 repository that is group-readable but not group-writable. 393 See linkgit:git-init[1]. False by default. 394 395core.warnAmbiguousRefs:: 396 If true, git will warn you if the ref name you passed it is ambiguous 397 and might match multiple refs in the .git/refs/ tree. True by default. 398 399core.compression:: 400 An integer -1..9, indicating a default compression level. 401 -1 is the zlib default. 0 means no compression, 402 and 1..9 are various speed/size tradeoffs, 9 being slowest. 403 If set, this provides a default to other compression variables, 404 such as 'core.loosecompression' and 'pack.compression'. 405 406core.loosecompression:: 407 An integer -1..9, indicating the compression level for objects that 408 are not in a pack file. -1 is the zlib default. 0 means no 409 compression, and 1..9 are various speed/size tradeoffs, 9 being 410 slowest. If not set, defaults to core.compression. If that is 411 not set, defaults to 1 (best speed). 412 413core.packedGitWindowSize:: 414 Number of bytes of a pack file to map into memory in a 415 single mapping operation. Larger window sizes may allow 416 your system to process a smaller number of large pack files 417 more quickly. Smaller window sizes will negatively affect 418 performance due to increased calls to the operating system's 419 memory manager, but may improve performance when accessing 420 a large number of large pack files. 421+ 422Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 423MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 424be reasonable for all users/operating systems. You probably do 425not need to adjust this value. 426+ 427Common unit suffixes of 'k', 'm', or 'g' are supported. 428 429core.packedGitLimit:: 430 Maximum number of bytes to map simultaneously into memory 431 from pack files. If Git needs to access more than this many 432 bytes at once to complete an operation it will unmap existing 433 regions to reclaim virtual address space within the process. 434+ 435Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 436This should be reasonable for all users/operating systems, except on 437the largest projects. You probably do not need to adjust this value. 438+ 439Common unit suffixes of 'k', 'm', or 'g' are supported. 440 441core.deltaBaseCacheLimit:: 442 Maximum number of bytes to reserve for caching base objects 443 that may be referenced by multiple deltified objects. By storing the 444 entire decompressed base objects in a cache Git is able 445 to avoid unpacking and decompressing frequently used base 446 objects multiple times. 447+ 448Default is 16 MiB on all platforms. This should be reasonable 449for all users/operating systems, except on the largest projects. 450You probably do not need to adjust this value. 451+ 452Common unit suffixes of 'k', 'm', or 'g' are supported. 453 454core.bigFileThreshold:: 455 Files larger than this size are stored deflated, without 456 attempting delta compression. Storing large files without 457 delta compression avoids excessive memory usage, at the 458 slight expense of increased disk usage. 459+ 460Default is 512 MiB on all platforms. This should be reasonable 461for most projects as source code and other text files can still 462be delta compressed, but larger binary media files won't be. 463+ 464Common unit suffixes of 'k', 'm', or 'g' are supported. 465 466core.excludesfile:: 467 In addition to '.gitignore' (per-directory) and 468 '.git/info/exclude', git looks into this file for patterns 469 of files which are not meant to be tracked. "{tilde}/" is expanded 470 to the value of `$HOME` and "{tilde}user/" to the specified user's 471 home directory. See linkgit:gitignore[5]. 472 473core.askpass:: 474 Some commands (e.g. svn and http interfaces) that interactively 475 ask for a password can be told to use an external program given 476 via the value of this variable. Can be overridden by the 'GIT_ASKPASS' 477 environment variable. If not set, fall back to the value of the 478 'SSH_ASKPASS' environment variable or, failing that, a simple password 479 prompt. The external program shall be given a suitable prompt as 480 command line argument and write the password on its STDOUT. 481 482core.attributesfile:: 483 In addition to '.gitattributes' (per-directory) and 484 '.git/info/attributes', git looks into this file for attributes 485 (see linkgit:gitattributes[5]). Path expansions are made the same 486 way as for `core.excludesfile`. 487 488core.editor:: 489 Commands such as `commit` and `tag` that lets you edit 490 messages by launching an editor uses the value of this 491 variable when it is set, and the environment variable 492 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 493 494sequence.editor:: 495 Text editor used by `git rebase -i` for editing the rebase insn file. 496 The value is meant to be interpreted by the shell when it is used. 497 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 498 When not configured the default commit message editor is used instead. 499 500core.pager:: 501 The command that git will use to paginate output. Can 502 be overridden with the `GIT_PAGER` environment 503 variable. Note that git sets the `LESS` environment 504 variable to `FRSX` if it is unset when it runs the 505 pager. One can change these settings by setting the 506 `LESS` variable to some other value. Alternately, 507 these settings can be overridden on a project or 508 global basis by setting the `core.pager` option. 509 Setting `core.pager` has no affect on the `LESS` 510 environment variable behaviour above, so if you want 511 to override git's default settings this way, you need 512 to be explicit. For example, to disable the S option 513 in a backward compatible manner, set `core.pager` 514 to `less -+$LESS -FRX`. This will be passed to the 515 shell by git, which will translate the final command to 516 `LESS=FRSX less -+FRSX -FRX`. 517 518core.whitespace:: 519 A comma separated list of common whitespace problems to 520 notice. 'git diff' will use `color.diff.whitespace` to 521 highlight them, and 'git apply --whitespace=error' will 522 consider them as errors. You can prefix `-` to disable 523 any of them (e.g. `-trailing-space`): 524+ 525* `blank-at-eol` treats trailing whitespaces at the end of the line 526 as an error (enabled by default). 527* `space-before-tab` treats a space character that appears immediately 528 before a tab character in the initial indent part of the line as an 529 error (enabled by default). 530* `indent-with-non-tab` treats a line that is indented with 8 or more 531 space characters as an error (not enabled by default). 532* `tab-in-indent` treats a tab character in the initial indent part of 533 the line as an error (not enabled by default). 534* `blank-at-eof` treats blank lines added at the end of file as an error 535 (enabled by default). 536* `trailing-space` is a short-hand to cover both `blank-at-eol` and 537 `blank-at-eof`. 538* `cr-at-eol` treats a carriage-return at the end of line as 539 part of the line terminator, i.e. with it, `trailing-space` 540 does not trigger if the character before such a carriage-return 541 is not a whitespace (not enabled by default). 542* `tabwidth=<n>` tells how many character positions a tab occupies; this 543 is relevant for `indent-with-non-tab` and when git fixes `tab-in-indent` 544 errors. The default tab width is 8. Allowed values are 1 to 63. 545 546core.fsyncobjectfiles:: 547 This boolean will enable 'fsync()' when writing object files. 548+ 549This is a total waste of time and effort on a filesystem that orders 550data writes properly, but can be useful for filesystems that do not use 551journalling (traditional UNIX filesystems) or that only journal metadata 552and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 553 554core.preloadindex:: 555 Enable parallel index preload for operations like 'git diff' 556+ 557This can speed up operations like 'git diff' and 'git status' especially 558on filesystems like NFS that have weak caching semantics and thus 559relatively high IO latencies. With this set to 'true', git will do the 560index comparison to the filesystem data in parallel, allowing 561overlapping IO's. 562 563core.createObject:: 564 You can set this to 'link', in which case a hardlink followed by 565 a delete of the source are used to make sure that object creation 566 will not overwrite existing objects. 567+ 568On some file system/operating system combinations, this is unreliable. 569Set this config setting to 'rename' there; However, This will remove the 570check that makes sure that existing object files will not get overwritten. 571 572core.notesRef:: 573 When showing commit messages, also show notes which are stored in 574 the given ref. The ref must be fully qualified. If the given 575 ref does not exist, it is not an error but means that no 576 notes should be printed. 577+ 578This setting defaults to "refs/notes/commits", and it can be overridden by 579the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1]. 580 581core.sparseCheckout:: 582 Enable "sparse checkout" feature. See section "Sparse checkout" in 583 linkgit:git-read-tree[1] for more information. 584 585core.abbrev:: 586 Set the length object names are abbreviated to. If unspecified, 587 many commands abbreviate to 7 hexdigits, which may not be enough 588 for abbreviated object names to stay unique for sufficiently long 589 time. 590 591add.ignore-errors:: 592add.ignoreErrors:: 593 Tells 'git add' to continue adding files when some files cannot be 594 added due to indexing errors. Equivalent to the '--ignore-errors' 595 option of linkgit:git-add[1]. Older versions of git accept only 596 `add.ignore-errors`, which does not follow the usual naming 597 convention for configuration variables. Newer versions of git 598 honor `add.ignoreErrors` as well. 599 600alias.*:: 601 Command aliases for the linkgit:git[1] command wrapper - e.g. 602 after defining "alias.last = cat-file commit HEAD", the invocation 603 "git last" is equivalent to "git cat-file commit HEAD". To avoid 604 confusion and troubles with script usage, aliases that 605 hide existing git commands are ignored. Arguments are split by 606 spaces, the usual shell quoting and escaping is supported. 607 quote pair and a backslash can be used to quote them. 608+ 609If the alias expansion is prefixed with an exclamation point, 610it will be treated as a shell command. For example, defining 611"alias.new = !gitk --all --not ORIG_HEAD", the invocation 612"git new" is equivalent to running the shell command 613"gitk --all --not ORIG_HEAD". Note that shell commands will be 614executed from the top-level directory of a repository, which may 615not necessarily be the current directory. 616'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix' 617from the original current directory. See linkgit:git-rev-parse[1]. 618 619am.keepcr:: 620 If true, git-am will call git-mailsplit for patches in mbox format 621 with parameter '--keep-cr'. In this case git-mailsplit will 622 not remove `\r` from lines ending with `\r\n`. Can be overridden 623 by giving '--no-keep-cr' from the command line. 624 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 625 626apply.ignorewhitespace:: 627 When set to 'change', tells 'git apply' to ignore changes in 628 whitespace, in the same way as the '--ignore-space-change' 629 option. 630 When set to one of: no, none, never, false tells 'git apply' to 631 respect all whitespace differences. 632 See linkgit:git-apply[1]. 633 634apply.whitespace:: 635 Tells 'git apply' how to handle whitespaces, in the same way 636 as the '--whitespace' option. See linkgit:git-apply[1]. 637 638branch.autosetupmerge:: 639 Tells 'git branch' and 'git checkout' to set up new branches 640 so that linkgit:git-pull[1] will appropriately merge from the 641 starting point branch. Note that even if this option is not set, 642 this behavior can be chosen per-branch using the `--track` 643 and `--no-track` options. The valid settings are: `false` -- no 644 automatic setup is done; `true` -- automatic setup is done when the 645 starting point is a remote-tracking branch; `always` -- 646 automatic setup is done when the starting point is either a 647 local branch or remote-tracking 648 branch. This option defaults to true. 649 650branch.autosetuprebase:: 651 When a new branch is created with 'git branch' or 'git checkout' 652 that tracks another branch, this variable tells git to set 653 up pull to rebase instead of merge (see "branch.<name>.rebase"). 654 When `never`, rebase is never automatically set to true. 655 When `local`, rebase is set to true for tracked branches of 656 other local branches. 657 When `remote`, rebase is set to true for tracked branches of 658 remote-tracking branches. 659 When `always`, rebase will be set to true for all tracking 660 branches. 661 See "branch.autosetupmerge" for details on how to set up a 662 branch to track another branch. 663 This option defaults to never. 664 665branch.<name>.remote:: 666 When in branch <name>, it tells 'git fetch' and 'git push' which 667 remote to fetch from/push to. It defaults to `origin` if no remote is 668 configured. `origin` is also used if you are not on any branch. 669 670branch.<name>.merge:: 671 Defines, together with branch.<name>.remote, the upstream branch 672 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which 673 branch to merge and can also affect 'git push' (see push.default). 674 When in branch <name>, it tells 'git fetch' the default 675 refspec to be marked for merging in FETCH_HEAD. The value is 676 handled like the remote part of a refspec, and must match a 677 ref which is fetched from the remote given by 678 "branch.<name>.remote". 679 The merge information is used by 'git pull' (which at first calls 680 'git fetch') to lookup the default branch for merging. Without 681 this option, 'git pull' defaults to merge the first refspec fetched. 682 Specify multiple values to get an octopus merge. 683 If you wish to setup 'git pull' so that it merges into <name> from 684 another branch in the local repository, you can point 685 branch.<name>.merge to the desired branch, and use the special setting 686 `.` (a period) for branch.<name>.remote. 687 688branch.<name>.mergeoptions:: 689 Sets default options for merging into branch <name>. The syntax and 690 supported options are the same as those of linkgit:git-merge[1], but 691 option values containing whitespace characters are currently not 692 supported. 693 694branch.<name>.rebase:: 695 When true, rebase the branch <name> on top of the fetched branch, 696 instead of merging the default branch from the default remote when 697 "git pull" is run. See "pull.rebase" for doing this in a non 698 branch-specific manner. 699+ 700*NOTE*: this is a possibly dangerous operation; do *not* use 701it unless you understand the implications (see linkgit:git-rebase[1] 702for details). 703 704browser.<tool>.cmd:: 705 Specify the command to invoke the specified browser. The 706 specified command is evaluated in shell with the URLs passed 707 as arguments. (See linkgit:git-web{litdd}browse[1].) 708 709browser.<tool>.path:: 710 Override the path for the given tool that may be used to 711 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 712 working repository in gitweb (see linkgit:git-instaweb[1]). 713 714clean.requireForce:: 715 A boolean to make git-clean do nothing unless given -f 716 or -n. Defaults to true. 717 718color.branch:: 719 A boolean to enable/disable color in the output of 720 linkgit:git-branch[1]. May be set to `always`, 721 `false` (or `never`) or `auto` (or `true`), in which case colors are used 722 only when the output is to a terminal. Defaults to false. 723 724color.branch.<slot>:: 725 Use customized color for branch coloration. `<slot>` is one of 726 `current` (the current branch), `local` (a local branch), 727 `remote` (a remote-tracking branch in refs/remotes/), `plain` (other 728 refs). 729+ 730The value for these configuration variables is a list of colors (at most 731two) and attributes (at most one), separated by spaces. The colors 732accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`, 733`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`, 734`blink` and `reverse`. The first color given is the foreground; the 735second is the background. The position of the attribute, if any, 736doesn't matter. 737 738color.diff:: 739 Whether to use ANSI escape sequences to add color to patches. 740 If this is set to `always`, linkgit:git-diff[1], 741 linkgit:git-log[1], and linkgit:git-show[1] will use color 742 for all patches. If it is set to `true` or `auto`, those 743 commands will only use color when output is to the terminal. 744 Defaults to false. 745+ 746This does not affect linkgit:git-format-patch[1] nor the 747'git-diff-{asterisk}' plumbing commands. Can be overridden on the 748command line with the `--color[=<when>]` option. 749 750color.diff.<slot>:: 751 Use customized color for diff colorization. `<slot>` specifies 752 which part of the patch to use the specified color, and is one 753 of `plain` (context text), `meta` (metainformation), `frag` 754 (hunk header), 'func' (function in hunk header), `old` (removed lines), 755 `new` (added lines), `commit` (commit headers), or `whitespace` 756 (highlighting whitespace errors). The values of these variables may be 757 specified as in color.branch.<slot>. 758 759color.decorate.<slot>:: 760 Use customized color for 'git log --decorate' output. `<slot>` is one 761 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local 762 branches, remote-tracking branches, tags, stash and HEAD, respectively. 763 764color.grep:: 765 When set to `always`, always highlight matches. When `false` (or 766 `never`), never. When set to `true` or `auto`, use color only 767 when the output is written to the terminal. Defaults to `false`. 768 769color.grep.<slot>:: 770 Use customized color for grep colorization. `<slot>` specifies which 771 part of the line to use the specified color, and is one of 772+ 773-- 774`context`;; 775 non-matching text in context lines (when using `-A`, `-B`, or `-C`) 776`filename`;; 777 filename prefix (when not using `-h`) 778`function`;; 779 function name lines (when using `-p`) 780`linenumber`;; 781 line number prefix (when using `-n`) 782`match`;; 783 matching text 784`selected`;; 785 non-matching text in selected lines 786`separator`;; 787 separators between fields on a line (`:`, `-`, and `=`) 788 and between hunks (`--`) 789-- 790+ 791The values of these variables may be specified as in color.branch.<slot>. 792 793color.interactive:: 794 When set to `always`, always use colors for interactive prompts 795 and displays (such as those used by "git-add --interactive"). 796 When false (or `never`), never. When set to `true` or `auto`, use 797 colors only when the output is to the terminal. Defaults to false. 798 799color.interactive.<slot>:: 800 Use customized color for 'git add --interactive' 801 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for 802 four distinct types of normal output from interactive 803 commands. The values of these variables may be specified as 804 in color.branch.<slot>. 805 806color.pager:: 807 A boolean to enable/disable colored output when the pager is in 808 use (default is true). 809 810color.showbranch:: 811 A boolean to enable/disable color in the output of 812 linkgit:git-show-branch[1]. May be set to `always`, 813 `false` (or `never`) or `auto` (or `true`), in which case colors are used 814 only when the output is to a terminal. Defaults to false. 815 816color.status:: 817 A boolean to enable/disable color in the output of 818 linkgit:git-status[1]. May be set to `always`, 819 `false` (or `never`) or `auto` (or `true`), in which case colors are used 820 only when the output is to a terminal. Defaults to false. 821 822color.status.<slot>:: 823 Use customized color for status colorization. `<slot>` is 824 one of `header` (the header text of the status message), 825 `added` or `updated` (files which are added but not committed), 826 `changed` (files which are changed but not added in the index), 827 `untracked` (files which are not tracked by git), 828 `branch` (the current branch), or 829 `nobranch` (the color the 'no branch' warning is shown in, defaulting 830 to red). The values of these variables may be specified as in 831 color.branch.<slot>. 832 833color.ui:: 834 This variable determines the default value for variables such 835 as `color.diff` and `color.grep` that control the use of color 836 per command family. Its scope will expand as more commands learn 837 configuration to set a default for the `--color` option. Set it 838 to `always` if you want all output not intended for machine 839 consumption to use color, to `true` or `auto` if you want such 840 output to use color when written to the terminal, or to `false` or 841 `never` if you prefer git commands not to use color unless enabled 842 explicitly with some other configuration or the `--color` option. 843 844commit.status:: 845 A boolean to enable/disable inclusion of status information in the 846 commit message template when using an editor to prepare the commit 847 message. Defaults to true. 848 849commit.template:: 850 Specify a file to use as the template for new commit messages. 851 "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the 852 specified user's home directory. 853 854credential.helper:: 855 Specify an external helper to be called when a username or 856 password credential is needed; the helper may consult external 857 storage to avoid prompting the user for the credentials. See 858 linkgit:gitcredentials[7] for details. 859 860credential.useHttpPath:: 861 When acquiring credentials, consider the "path" component of an http 862 or https URL to be important. Defaults to false. See 863 linkgit:gitcredentials[7] for more information. 864 865credential.username:: 866 If no username is set for a network authentication, use this username 867 by default. See credential.<context>.* below, and 868 linkgit:gitcredentials[7]. 869 870credential.<url>.*:: 871 Any of the credential.* options above can be applied selectively to 872 some credentials. For example "credential.https://example.com.username" 873 would set the default username only for https connections to 874 example.com. See linkgit:gitcredentials[7] for details on how URLs are 875 matched. 876 877include::diff-config.txt[] 878 879difftool.<tool>.path:: 880 Override the path for the given tool. This is useful in case 881 your tool is not in the PATH. 882 883difftool.<tool>.cmd:: 884 Specify the command to invoke the specified diff tool. 885 The specified command is evaluated in shell with the following 886 variables available: 'LOCAL' is set to the name of the temporary 887 file containing the contents of the diff pre-image and 'REMOTE' 888 is set to the name of the temporary file containing the contents 889 of the diff post-image. 890 891difftool.prompt:: 892 Prompt before each invocation of the diff tool. 893 894diff.wordRegex:: 895 A POSIX Extended Regular Expression used to determine what is a "word" 896 when performing word-by-word difference calculations. Character 897 sequences that match the regular expression are "words", all other 898 characters are *ignorable* whitespace. 899 900fetch.recurseSubmodules:: 901 This option can be either set to a boolean value or to 'on-demand'. 902 Setting it to a boolean changes the behavior of fetch and pull to 903 unconditionally recurse into submodules when set to true or to not 904 recurse at all when set to false. When set to 'on-demand' (the default 905 value), fetch and pull will only recurse into a populated submodule 906 when its superproject retrieves a commit that updates the submodule's 907 reference. 908 909fetch.fsckObjects:: 910 If it is set to true, git-fetch-pack will check all fetched 911 objects. It will abort in the case of a malformed object or a 912 broken link. The result of an abort are only dangling objects. 913 Defaults to false. If not set, the value of `transfer.fsckObjects` 914 is used instead. 915 916fetch.unpackLimit:: 917 If the number of objects fetched over the git native 918 transfer is below this 919 limit, then the objects will be unpacked into loose object 920 files. However if the number of received objects equals or 921 exceeds this limit then the received pack will be stored as 922 a pack, after adding any missing delta bases. Storing the 923 pack from a push can make the push operation complete faster, 924 especially on slow filesystems. If not set, the value of 925 `transfer.unpackLimit` is used instead. 926 927format.attach:: 928 Enable multipart/mixed attachments as the default for 929 'format-patch'. The value can also be a double quoted string 930 which will enable attachments as the default and set the 931 value as the boundary. See the --attach option in 932 linkgit:git-format-patch[1]. 933 934format.numbered:: 935 A boolean which can enable or disable sequence numbers in patch 936 subjects. It defaults to "auto" which enables it only if there 937 is more than one patch. It can be enabled or disabled for all 938 messages by setting it to "true" or "false". See --numbered 939 option in linkgit:git-format-patch[1]. 940 941format.headers:: 942 Additional email headers to include in a patch to be submitted 943 by mail. See linkgit:git-format-patch[1]. 944 945format.to:: 946format.cc:: 947 Additional recipients to include in a patch to be submitted 948 by mail. See the --to and --cc options in 949 linkgit:git-format-patch[1]. 950 951format.subjectprefix:: 952 The default for format-patch is to output files with the '[PATCH]' 953 subject prefix. Use this variable to change that prefix. 954 955format.signature:: 956 The default for format-patch is to output a signature containing 957 the git version number. Use this variable to change that default. 958 Set this variable to the empty string ("") to suppress 959 signature generation. 960 961format.suffix:: 962 The default for format-patch is to output files with the suffix 963 `.patch`. Use this variable to change that suffix (make sure to 964 include the dot if you want it). 965 966format.pretty:: 967 The default pretty format for log/show/whatchanged command, 968 See linkgit:git-log[1], linkgit:git-show[1], 969 linkgit:git-whatchanged[1]. 970 971format.thread:: 972 The default threading style for 'git format-patch'. Can be 973 a boolean value, or `shallow` or `deep`. `shallow` threading 974 makes every mail a reply to the head of the series, 975 where the head is chosen from the cover letter, the 976 `\--in-reply-to`, and the first patch mail, in this order. 977 `deep` threading makes every mail a reply to the previous one. 978 A true boolean value is the same as `shallow`, and a false 979 value disables threading. 980 981format.signoff:: 982 A boolean value which lets you enable the `-s/--signoff` option of 983 format-patch by default. *Note:* Adding the Signed-off-by: line to a 984 patch should be a conscious act and means that you certify you have 985 the rights to submit this work under the same open source license. 986 Please see the 'SubmittingPatches' document for further discussion. 987 988filter.<driver>.clean:: 989 The command which is used to convert the content of a worktree 990 file to a blob upon checkin. See linkgit:gitattributes[5] for 991 details. 992 993filter.<driver>.smudge:: 994 The command which is used to convert the content of a blob 995 object to a worktree file upon checkout. See 996 linkgit:gitattributes[5] for details. 997 998gc.aggressiveWindow:: 999 The window size parameter used in the delta compression1000 algorithm used by 'git gc --aggressive'. This defaults1001 to 250.10021003gc.auto::1004 When there are approximately more than this many loose1005 objects in the repository, `git gc --auto` will pack them.1006 Some Porcelain commands use this command to perform a1007 light-weight garbage collection from time to time. The1008 default value is 6700. Setting this to 0 disables it.10091010gc.autopacklimit::1011 When there are more than this many packs that are not1012 marked with `*.keep` file in the repository, `git gc1013 --auto` consolidates them into one larger pack. The1014 default value is 50. Setting this to 0 disables it.10151016gc.packrefs::1017 Running `git pack-refs` in a repository renders it1018 unclonable by Git versions prior to 1.5.1.2 over dumb1019 transports such as HTTP. This variable determines whether1020 'git gc' runs `git pack-refs`. This can be set to `notbare`1021 to enable it within all non-bare repos or it can be set to a1022 boolean value. The default is `true`.10231024gc.pruneexpire::1025 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1026 Override the grace period with this config variable. The value1027 "now" may be used to disable this grace period and always prune1028 unreachable objects immediately.10291030gc.reflogexpire::1031gc.<pattern>.reflogexpire::1032 'git reflog expire' removes reflog entries older than1033 this time; defaults to 90 days. With "<pattern>" (e.g.1034 "refs/stash") in the middle the setting applies only to1035 the refs that match the <pattern>.10361037gc.reflogexpireunreachable::1038gc.<ref>.reflogexpireunreachable::1039 'git reflog expire' removes reflog entries older than1040 this time and are not reachable from the current tip;1041 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")1042 in the middle, the setting applies only to the refs that1043 match the <pattern>.10441045gc.rerereresolved::1046 Records of conflicted merge you resolved earlier are1047 kept for this many days when 'git rerere gc' is run.1048 The default is 60 days. See linkgit:git-rerere[1].10491050gc.rerereunresolved::1051 Records of conflicted merge you have not resolved are1052 kept for this many days when 'git rerere gc' is run.1053 The default is 15 days. See linkgit:git-rerere[1].10541055gitcvs.commitmsgannotation::1056 Append this string to each commit message. Set to empty string1057 to disable this feature. Defaults to "via git-CVS emulator".10581059gitcvs.enabled::1060 Whether the CVS server interface is enabled for this repository.1061 See linkgit:git-cvsserver[1].10621063gitcvs.logfile::1064 Path to a log file where the CVS server interface well... logs1065 various stuff. See linkgit:git-cvsserver[1].10661067gitcvs.usecrlfattr::1068 If true, the server will look up the end-of-line conversion1069 attributes for files to determine the '-k' modes to use. If1070 the attributes force git to treat a file as text,1071 the '-k' mode will be left blank so CVS clients will1072 treat it as text. If they suppress text conversion, the file1073 will be set with '-kb' mode, which suppresses any newline munging1074 the client might otherwise do. If the attributes do not allow1075 the file type to be determined, then 'gitcvs.allbinary' is1076 used. See linkgit:gitattributes[5].10771078gitcvs.allbinary::1079 This is used if 'gitcvs.usecrlfattr' does not resolve1080 the correct '-kb' mode to use. If true, all1081 unresolved files are sent to the client in1082 mode '-kb'. This causes the client to treat them1083 as binary files, which suppresses any newline munging it1084 otherwise might do. Alternatively, if it is set to "guess",1085 then the contents of the file are examined to decide if1086 it is binary, similar to 'core.autocrlf'.10871088gitcvs.dbname::1089 Database used by git-cvsserver to cache revision information1090 derived from the git repository. The exact meaning depends on the1091 used database driver, for SQLite (which is the default driver) this1092 is a filename. Supports variable substitution (see1093 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1094 Default: '%Ggitcvs.%m.sqlite'10951096gitcvs.dbdriver::1097 Used Perl DBI driver. You can specify any available driver1098 for this here, but it might not work. git-cvsserver is tested1099 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1100 reported *not* to work with 'DBD::mysql'. Experimental feature.1101 May not contain double colons (`:`). Default: 'SQLite'.1102 See linkgit:git-cvsserver[1].11031104gitcvs.dbuser, gitcvs.dbpass::1105 Database user and password. Only useful if setting 'gitcvs.dbdriver',1106 since SQLite has no concept of database users and/or passwords.1107 'gitcvs.dbuser' supports variable substitution (see1108 linkgit:git-cvsserver[1] for details).11091110gitcvs.dbTableNamePrefix::1111 Database table name prefix. Prepended to the names of any1112 database tables used, allowing a single database to be used1113 for several repositories. Supports variable substitution (see1114 linkgit:git-cvsserver[1] for details). Any non-alphabetic1115 characters will be replaced with underscores.11161117All gitcvs variables except for 'gitcvs.usecrlfattr' and1118'gitcvs.allbinary' can also be specified as1119'gitcvs.<access_method>.<varname>' (where 'access_method'1120is one of "ext" and "pserver") to make them apply only for the given1121access method.11221123gitweb.category::1124gitweb.description::1125gitweb.owner::1126gitweb.url::1127 See linkgit:gitweb[1] for description.11281129gitweb.avatar::1130gitweb.blame::1131gitweb.grep::1132gitweb.highlight::1133gitweb.patches::1134gitweb.pickaxe::1135gitweb.remote_heads::1136gitweb.showsizes::1137gitweb.snapshot::1138 See linkgit:gitweb.conf[5] for description.11391140grep.lineNumber::1141 If set to true, enable '-n' option by default.11421143grep.extendedRegexp::1144 If set to true, enable '--extended-regexp' option by default.11451146gpg.program::1147 Use this custom program instead of "gpg" found on $PATH when1148 making or verifying a PGP signature. The program must support the1149 same command line interface as GPG, namely, to verify a detached1150 signature, "gpg --verify $file - <$signature" is run, and the1151 program is expected to signal a good signature by exiting with1152 code 0, and to generate an ascii-armored detached signature, the1153 standard input of "gpg -bsau $key" is fed with the contents to be1154 signed, and the program is expected to send the result to its1155 standard output.11561157gui.commitmsgwidth::1158 Defines how wide the commit message window is in the1159 linkgit:git-gui[1]. "75" is the default.11601161gui.diffcontext::1162 Specifies how many context lines should be used in calls to diff1163 made by the linkgit:git-gui[1]. The default is "5".11641165gui.encoding::1166 Specifies the default encoding to use for displaying of1167 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1168 It can be overridden by setting the 'encoding' attribute1169 for relevant files (see linkgit:gitattributes[5]).1170 If this option is not set, the tools default to the1171 locale encoding.11721173gui.matchtrackingbranch::1174 Determines if new branches created with linkgit:git-gui[1] should1175 default to tracking remote branches with matching names or1176 not. Default: "false".11771178gui.newbranchtemplate::1179 Is used as suggested name when creating new branches using the1180 linkgit:git-gui[1].11811182gui.pruneduringfetch::1183 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1184 performing a fetch. The default value is "false".11851186gui.trustmtime::1187 Determines if linkgit:git-gui[1] should trust the file modification1188 timestamp or not. By default the timestamps are not trusted.11891190gui.spellingdictionary::1191 Specifies the dictionary used for spell checking commit messages in1192 the linkgit:git-gui[1]. When set to "none" spell checking is turned1193 off.11941195gui.fastcopyblame::1196 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1197 location detection. It makes blame significantly faster on huge1198 repositories at the expense of less thorough copy detection.11991200gui.copyblamethreshold::1201 Specifies the threshold to use in 'git gui blame' original location1202 detection, measured in alphanumeric characters. See the1203 linkgit:git-blame[1] manual for more information on copy detection.12041205gui.blamehistoryctx::1206 Specifies the radius of history context in days to show in1207 linkgit:gitk[1] for the selected commit, when the `Show History1208 Context` menu item is invoked from 'git gui blame'. If this1209 variable is set to zero, the whole history is shown.12101211guitool.<name>.cmd::1212 Specifies the shell command line to execute when the corresponding item1213 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1214 mandatory for every tool. The command is executed from the root of1215 the working directory, and in the environment it receives the name of1216 the tool as 'GIT_GUITOOL', the name of the currently selected file as1217 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1218 the head is detached, 'CUR_BRANCH' is empty).12191220guitool.<name>.needsfile::1221 Run the tool only if a diff is selected in the GUI. It guarantees1222 that 'FILENAME' is not empty.12231224guitool.<name>.noconsole::1225 Run the command silently, without creating a window to display its1226 output.12271228guitool.<name>.norescan::1229 Don't rescan the working directory for changes after the tool1230 finishes execution.12311232guitool.<name>.confirm::1233 Show a confirmation dialog before actually running the tool.12341235guitool.<name>.argprompt::1236 Request a string argument from the user, and pass it to the tool1237 through the 'ARGS' environment variable. Since requesting an1238 argument implies confirmation, the 'confirm' option has no effect1239 if this is enabled. If the option is set to 'true', 'yes', or '1',1240 the dialog uses a built-in generic prompt; otherwise the exact1241 value of the variable is used.12421243guitool.<name>.revprompt::1244 Request a single valid revision from the user, and set the1245 'REVISION' environment variable. In other aspects this option1246 is similar to 'argprompt', and can be used together with it.12471248guitool.<name>.revunmerged::1249 Show only unmerged branches in the 'revprompt' subdialog.1250 This is useful for tools similar to merge or rebase, but not1251 for things like checkout or reset.12521253guitool.<name>.title::1254 Specifies the title to use for the prompt dialog. The default1255 is the tool name.12561257guitool.<name>.prompt::1258 Specifies the general prompt string to display at the top of1259 the dialog, before subsections for 'argprompt' and 'revprompt'.1260 The default value includes the actual command.12611262help.browser::1263 Specify the browser that will be used to display help in the1264 'web' format. See linkgit:git-help[1].12651266help.format::1267 Override the default help format used by linkgit:git-help[1].1268 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1269 the default. 'web' and 'html' are the same.12701271help.autocorrect::1272 Automatically correct and execute mistyped commands after1273 waiting for the given number of deciseconds (0.1 sec). If more1274 than one command can be deduced from the entered text, nothing1275 will be executed. If the value of this option is negative,1276 the corrected command will be executed immediately. If the1277 value is 0 - the command will be just shown but not executed.1278 This is the default.12791280http.proxy::1281 Override the HTTP proxy, normally configured using the 'http_proxy',1282 'https_proxy', and 'all_proxy' environment variables (see1283 `curl(1)`). This can be overridden on a per-remote basis; see1284 remote.<name>.proxy12851286http.cookiefile::1287 File containing previously stored cookie lines which should be used1288 in the git http session, if they match the server. The file format1289 of the file to read cookies from should be plain HTTP headers or1290 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).1291 NOTE that the file specified with http.cookiefile is only used as1292 input. No cookies will be stored in the file.12931294http.sslVerify::1295 Whether to verify the SSL certificate when fetching or pushing1296 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1297 variable.12981299http.sslCert::1300 File containing the SSL certificate when fetching or pushing1301 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1302 variable.13031304http.sslKey::1305 File containing the SSL private key when fetching or pushing1306 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1307 variable.13081309http.sslCertPasswordProtected::1310 Enable git's password prompt for the SSL certificate. Otherwise1311 OpenSSL will prompt the user, possibly many times, if the1312 certificate or private key is encrypted. Can be overridden by the1313 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.13141315http.sslCAInfo::1316 File containing the certificates to verify the peer with when1317 fetching or pushing over HTTPS. Can be overridden by the1318 'GIT_SSL_CAINFO' environment variable.13191320http.sslCAPath::1321 Path containing files with the CA certificates to verify the peer1322 with when fetching or pushing over HTTPS. Can be overridden1323 by the 'GIT_SSL_CAPATH' environment variable.13241325http.maxRequests::1326 How many HTTP requests to launch in parallel. Can be overridden1327 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.13281329http.minSessions::1330 The number of curl sessions (counted across slots) to be kept across1331 requests. They will not be ended with curl_easy_cleanup() until1332 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1333 value will be capped at 1. Defaults to 1.13341335http.postBuffer::1336 Maximum size in bytes of the buffer used by smart HTTP1337 transports when POSTing data to the remote system.1338 For requests larger than this buffer size, HTTP/1.1 and1339 Transfer-Encoding: chunked is used to avoid creating a1340 massive pack file locally. Default is 1 MiB, which is1341 sufficient for most requests.13421343http.lowSpeedLimit, http.lowSpeedTime::1344 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1345 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1346 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1347 'GIT_HTTP_LOW_SPEED_TIME' environment variables.13481349http.noEPSV::1350 A boolean which disables using of EPSV ftp command by curl.1351 This can helpful with some "poor" ftp servers which don't1352 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1353 environment variable. Default is false (curl will use EPSV).13541355http.useragent::1356 The HTTP USER_AGENT string presented to an HTTP server. The default1357 value represents the version of the client git such as git/1.7.1.1358 This option allows you to override this value to a more common value1359 such as Mozilla/4.0. This may be necessary, for instance, if1360 connecting through a firewall that restricts HTTP connections to a set1361 of common USER_AGENT strings (but not including those like git/1.7.1).1362 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.13631364i18n.commitEncoding::1365 Character encoding the commit messages are stored in; git itself1366 does not care per se, but this information is necessary e.g. when1367 importing commits from emails or in the gitk graphical history1368 browser (and possibly at other places in the future or in other1369 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.13701371i18n.logOutputEncoding::1372 Character encoding the commit messages are converted to when1373 running 'git log' and friends.13741375imap::1376 The configuration variables in the 'imap' section are described1377 in linkgit:git-imap-send[1].13781379init.templatedir::1380 Specify the directory from which templates will be copied.1381 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)13821383instaweb.browser::1384 Specify the program that will be used to browse your working1385 repository in gitweb. See linkgit:git-instaweb[1].13861387instaweb.httpd::1388 The HTTP daemon command-line to start gitweb on your working1389 repository. See linkgit:git-instaweb[1].13901391instaweb.local::1392 If true the web server started by linkgit:git-instaweb[1] will1393 be bound to the local IP (127.0.0.1).13941395instaweb.modulepath::1396 The default module path for linkgit:git-instaweb[1] to use1397 instead of /usr/lib/apache2/modules. Only used if httpd1398 is Apache.13991400instaweb.port::1401 The port number to bind the gitweb httpd to. See1402 linkgit:git-instaweb[1].14031404interactive.singlekey::1405 In interactive commands, allow the user to provide one-letter1406 input with a single key (i.e., without hitting enter).1407 Currently this is used by the `\--patch` mode of1408 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],1409 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this1410 setting is silently ignored if portable keystroke input1411 is not available.14121413log.abbrevCommit::1414 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1415 linkgit:git-whatchanged[1] assume `\--abbrev-commit`. You may1416 override this option with `\--no-abbrev-commit`.14171418log.date::1419 Set the default date-time mode for the 'log' command.1420 Setting a value for log.date is similar to using 'git log''s1421 `\--date` option. Possible values are `relative`, `local`,1422 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]1423 for details.14241425log.decorate::1426 Print out the ref names of any commits that are shown by the log1427 command. If 'short' is specified, the ref name prefixes 'refs/heads/',1428 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is1429 specified, the full ref name (including prefix) will be printed.1430 This is the same as the log commands '--decorate' option.14311432log.showroot::1433 If true, the initial commit will be shown as a big creation event.1434 This is equivalent to a diff against an empty tree.1435 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1436 normally hide the root commit will now show it. True by default.14371438mailmap.file::1439 The location of an augmenting mailmap file. The default1440 mailmap, located in the root of the repository, is loaded1441 first, then the mailmap file pointed to by this variable.1442 The location of the mailmap file may be in a repository1443 subdirectory, or somewhere outside of the repository itself.1444 See linkgit:git-shortlog[1] and linkgit:git-blame[1].14451446man.viewer::1447 Specify the programs that may be used to display help in the1448 'man' format. See linkgit:git-help[1].14491450man.<tool>.cmd::1451 Specify the command to invoke the specified man viewer. The1452 specified command is evaluated in shell with the man page1453 passed as argument. (See linkgit:git-help[1].)14541455man.<tool>.path::1456 Override the path for the given tool that may be used to1457 display help in the 'man' format. See linkgit:git-help[1].14581459include::merge-config.txt[]14601461mergetool.<tool>.path::1462 Override the path for the given tool. This is useful in case1463 your tool is not in the PATH.14641465mergetool.<tool>.cmd::1466 Specify the command to invoke the specified merge tool. The1467 specified command is evaluated in shell with the following1468 variables available: 'BASE' is the name of a temporary file1469 containing the common base of the files to be merged, if available;1470 'LOCAL' is the name of a temporary file containing the contents of1471 the file on the current branch; 'REMOTE' is the name of a temporary1472 file containing the contents of the file from the branch being1473 merged; 'MERGED' contains the name of the file to which the merge1474 tool should write the results of a successful merge.14751476mergetool.<tool>.trustExitCode::1477 For a custom merge command, specify whether the exit code of1478 the merge command can be used to determine whether the merge was1479 successful. If this is not set to true then the merge target file1480 timestamp is checked and the merge assumed to have been successful1481 if the file has been updated, otherwise the user is prompted to1482 indicate the success of the merge.14831484mergetool.keepBackup::1485 After performing a merge, the original file with conflict markers1486 can be saved as a file with a `.orig` extension. If this variable1487 is set to `false` then this file is not preserved. Defaults to1488 `true` (i.e. keep the backup files).14891490mergetool.keepTemporaries::1491 When invoking a custom merge tool, git uses a set of temporary1492 files to pass to the tool. If the tool returns an error and this1493 variable is set to `true`, then these temporary files will be1494 preserved, otherwise they will be removed after the tool has1495 exited. Defaults to `false`.14961497mergetool.prompt::1498 Prompt before each invocation of the merge resolution program.14991500notes.displayRef::1501 The (fully qualified) refname from which to show notes when1502 showing commit messages. The value of this variable can be set1503 to a glob, in which case notes from all matching refs will be1504 shown. You may also specify this configuration variable1505 several times. A warning will be issued for refs that do not1506 exist, but a glob that does not match any refs is silently1507 ignored.1508+1509This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`1510environment variable, which must be a colon separated list of refs or1511globs.1512+1513The effective value of "core.notesRef" (possibly overridden by1514GIT_NOTES_REF) is also implicitly added to the list of refs to be1515displayed.15161517notes.rewrite.<command>::1518 When rewriting commits with <command> (currently `amend` or1519 `rebase`) and this variable is set to `true`, git1520 automatically copies your notes from the original to the1521 rewritten commit. Defaults to `true`, but see1522 "notes.rewriteRef" below.15231524notes.rewriteMode::1525 When copying notes during a rewrite (see the1526 "notes.rewrite.<command>" option), determines what to do if1527 the target commit already has a note. Must be one of1528 `overwrite`, `concatenate`, or `ignore`. Defaults to1529 `concatenate`.1530+1531This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`1532environment variable.15331534notes.rewriteRef::1535 When copying notes during a rewrite, specifies the (fully1536 qualified) ref whose notes should be copied. The ref may be a1537 glob, in which case notes in all matching refs will be copied.1538 You may also specify this configuration several times.1539+1540Does not have a default value; you must configure this variable to1541enable note rewriting. Set it to `refs/notes/commits` to enable1542rewriting for the default commit notes.1543+1544This setting can be overridden with the `GIT_NOTES_REWRITE_REF`1545environment variable, which must be a colon separated list of refs or1546globs.15471548pack.window::1549 The size of the window used by linkgit:git-pack-objects[1] when no1550 window size is given on the command line. Defaults to 10.15511552pack.depth::1553 The maximum delta depth used by linkgit:git-pack-objects[1] when no1554 maximum depth is given on the command line. Defaults to 50.15551556pack.windowMemory::1557 The window memory size limit used by linkgit:git-pack-objects[1]1558 when no limit is given on the command line. The value can be1559 suffixed with "k", "m", or "g". Defaults to 0, meaning no1560 limit.15611562pack.compression::1563 An integer -1..9, indicating the compression level for objects1564 in a pack file. -1 is the zlib default. 0 means no1565 compression, and 1..9 are various speed/size tradeoffs, 9 being1566 slowest. If not set, defaults to core.compression. If that is1567 not set, defaults to -1, the zlib default, which is "a default1568 compromise between speed and compression (currently equivalent1569 to level 6)."1570+1571Note that changing the compression level will not automatically recompress1572all existing objects. You can force recompression by passing the -F option1573to linkgit:git-repack[1].15741575pack.deltaCacheSize::1576 The maximum memory in bytes used for caching deltas in1577 linkgit:git-pack-objects[1] before writing them out to a pack.1578 This cache is used to speed up the writing object phase by not1579 having to recompute the final delta result once the best match1580 for all objects is found. Repacking large repositories on machines1581 which are tight with memory might be badly impacted by this though,1582 especially if this cache pushes the system into swapping.1583 A value of 0 means no limit. The smallest size of 1 byte may be1584 used to virtually disable this cache. Defaults to 256 MiB.15851586pack.deltaCacheLimit::1587 The maximum size of a delta, that is cached in1588 linkgit:git-pack-objects[1]. This cache is used to speed up the1589 writing object phase by not having to recompute the final delta1590 result once the best match for all objects is found. Defaults to 1000.15911592pack.threads::1593 Specifies the number of threads to spawn when searching for best1594 delta matches. This requires that linkgit:git-pack-objects[1]1595 be compiled with pthreads otherwise this option is ignored with a1596 warning. This is meant to reduce packing time on multiprocessor1597 machines. The required amount of memory for the delta search window1598 is however multiplied by the number of threads.1599 Specifying 0 will cause git to auto-detect the number of CPU's1600 and set the number of threads accordingly.16011602pack.indexVersion::1603 Specify the default pack index version. Valid values are 1 for1604 legacy pack index used by Git versions prior to 1.5.2, and 2 for1605 the new pack index with capabilities for packs larger than 4 GB1606 as well as proper protection against the repacking of corrupted1607 packs. Version 2 is the default. Note that version 2 is enforced1608 and this config option ignored whenever the corresponding pack is1609 larger than 2 GB.1610+1611If you have an old git that does not understand the version 2 `{asterisk}.idx` file,1612cloning or fetching over a non native protocol (e.g. "http" and "rsync")1613that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the1614other side may give you a repository that cannot be accessed with your1615older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,1616you can use linkgit:git-index-pack[1] on the *.pack file to regenerate1617the `{asterisk}.idx` file.16181619pack.packSizeLimit::1620 The maximum size of a pack. This setting only affects1621 packing to a file when repacking, i.e. the git:// protocol1622 is unaffected. It can be overridden by the `\--max-pack-size`1623 option of linkgit:git-repack[1]. The minimum size allowed is1624 limited to 1 MiB. The default is unlimited.1625 Common unit suffixes of 'k', 'm', or 'g' are1626 supported.16271628pager.<cmd>::1629 If the value is boolean, turns on or off pagination of the1630 output of a particular git subcommand when writing to a tty.1631 Otherwise, turns on pagination for the subcommand using the1632 pager specified by the value of `pager.<cmd>`. If `\--paginate`1633 or `\--no-pager` is specified on the command line, it takes1634 precedence over this option. To disable pagination for all1635 commands, set `core.pager` or `GIT_PAGER` to `cat`.16361637pretty.<name>::1638 Alias for a --pretty= format string, as specified in1639 linkgit:git-log[1]. Any aliases defined here can be used just1640 as the built-in pretty formats could. For example,1641 running `git config pretty.changelog "format:{asterisk} %H %s"`1642 would cause the invocation `git log --pretty=changelog`1643 to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.1644 Note that an alias with the same name as a built-in format1645 will be silently ignored.16461647pull.rebase::1648 When true, rebase branches on top of the fetched branch, instead1649 of merging the default branch from the default remote when "git1650 pull" is run. See "branch.<name>.rebase" for setting this on a1651 per-branch basis.1652+1653*NOTE*: this is a possibly dangerous operation; do *not* use1654it unless you understand the implications (see linkgit:git-rebase[1]1655for details).16561657pull.octopus::1658 The default merge strategy to use when pulling multiple branches1659 at once.16601661pull.twohead::1662 The default merge strategy to use when pulling a single branch.16631664push.default::1665 Defines the action git push should take if no refspec is given1666 on the command line, no refspec is configured in the remote, and1667 no refspec is implied by any of the options given on the command1668 line. Possible values are:1669+1670* `nothing` - do not push anything.1671* `matching` - push all matching branches.1672 All branches having the same name in both ends are considered to be1673 matching. This is the default.1674* `upstream` - push the current branch to its upstream branch.1675* `tracking` - deprecated synonym for `upstream`.1676* `current` - push the current branch to a branch of the same name.16771678rebase.stat::1679 Whether to show a diffstat of what changed upstream since the last1680 rebase. False by default.16811682rebase.autosquash::1683 If set to true enable '--autosquash' option by default.16841685receive.autogc::1686 By default, git-receive-pack will run "git-gc --auto" after1687 receiving data from git-push and updating refs. You can stop1688 it by setting this variable to false.16891690receive.fsckObjects::1691 If it is set to true, git-receive-pack will check all received1692 objects. It will abort in the case of a malformed object or a1693 broken link. The result of an abort are only dangling objects.1694 Defaults to false. If not set, the value of `transfer.fsckObjects`1695 is used instead.16961697receive.unpackLimit::1698 If the number of objects received in a push is below this1699 limit then the objects will be unpacked into loose object1700 files. However if the number of received objects equals or1701 exceeds this limit then the received pack will be stored as1702 a pack, after adding any missing delta bases. Storing the1703 pack from a push can make the push operation complete faster,1704 especially on slow filesystems. If not set, the value of1705 `transfer.unpackLimit` is used instead.17061707receive.denyDeletes::1708 If set to true, git-receive-pack will deny a ref update that deletes1709 the ref. Use this to prevent such a ref deletion via a push.17101711receive.denyDeleteCurrent::1712 If set to true, git-receive-pack will deny a ref update that1713 deletes the currently checked out branch of a non-bare repository.17141715receive.denyCurrentBranch::1716 If set to true or "refuse", git-receive-pack will deny a ref update1717 to the currently checked out branch of a non-bare repository.1718 Such a push is potentially dangerous because it brings the HEAD1719 out of sync with the index and working tree. If set to "warn",1720 print a warning of such a push to stderr, but allow the push to1721 proceed. If set to false or "ignore", allow such pushes with no1722 message. Defaults to "refuse".17231724receive.denyNonFastForwards::1725 If set to true, git-receive-pack will deny a ref update which is1726 not a fast-forward. Use this to prevent such an update via a push,1727 even if that push is forced. This configuration variable is1728 set when initializing a shared repository.17291730receive.updateserverinfo::1731 If set to true, git-receive-pack will run git-update-server-info1732 after receiving data from git-push and updating refs.17331734remote.<name>.url::1735 The URL of a remote repository. See linkgit:git-fetch[1] or1736 linkgit:git-push[1].17371738remote.<name>.pushurl::1739 The push URL of a remote repository. See linkgit:git-push[1].17401741remote.<name>.proxy::1742 For remotes that require curl (http, https and ftp), the URL to1743 the proxy to use for that remote. Set to the empty string to1744 disable proxying for that remote.17451746remote.<name>.fetch::1747 The default set of "refspec" for linkgit:git-fetch[1]. See1748 linkgit:git-fetch[1].17491750remote.<name>.push::1751 The default set of "refspec" for linkgit:git-push[1]. See1752 linkgit:git-push[1].17531754remote.<name>.mirror::1755 If true, pushing to this remote will automatically behave1756 as if the `\--mirror` option was given on the command line.17571758remote.<name>.skipDefaultUpdate::1759 If true, this remote will be skipped by default when updating1760 using linkgit:git-fetch[1] or the `update` subcommand of1761 linkgit:git-remote[1].17621763remote.<name>.skipFetchAll::1764 If true, this remote will be skipped by default when updating1765 using linkgit:git-fetch[1] or the `update` subcommand of1766 linkgit:git-remote[1].17671768remote.<name>.receivepack::1769 The default program to execute on the remote side when pushing. See1770 option \--receive-pack of linkgit:git-push[1].17711772remote.<name>.uploadpack::1773 The default program to execute on the remote side when fetching. See1774 option \--upload-pack of linkgit:git-fetch-pack[1].17751776remote.<name>.tagopt::1777 Setting this value to \--no-tags disables automatic tag following when1778 fetching from remote <name>. Setting it to \--tags will fetch every1779 tag from remote <name>, even if they are not reachable from remote1780 branch heads. Passing these flags directly to linkgit:git-fetch[1] can1781 override this setting. See options \--tags and \--no-tags of1782 linkgit:git-fetch[1].17831784remote.<name>.vcs::1785 Setting this to a value <vcs> will cause git to interact with1786 the remote with the git-remote-<vcs> helper.17871788remotes.<group>::1789 The list of remotes which are fetched by "git remote update1790 <group>". See linkgit:git-remote[1].17911792repack.usedeltabaseoffset::1793 By default, linkgit:git-repack[1] creates packs that use1794 delta-base offset. If you need to share your repository with1795 git older than version 1.4.4, either directly or via a dumb1796 protocol such as http, then you need to set this option to1797 "false" and repack. Access from old git versions over the1798 native protocol are unaffected by this option.17991800rerere.autoupdate::1801 When set to true, `git-rerere` updates the index with the1802 resulting contents after it cleanly resolves conflicts using1803 previously recorded resolution. Defaults to false.18041805rerere.enabled::1806 Activate recording of resolved conflicts, so that identical1807 conflict hunks can be resolved automatically, should they be1808 encountered again. By default, linkgit:git-rerere[1] is1809 enabled if there is an `rr-cache` directory under the1810 `$GIT_DIR`, e.g. if "rerere" was previously used in the1811 repository.18121813sendemail.identity::1814 A configuration identity. When given, causes values in the1815 'sendemail.<identity>' subsection to take precedence over1816 values in the 'sendemail' section. The default identity is1817 the value of 'sendemail.identity'.18181819sendemail.smtpencryption::1820 See linkgit:git-send-email[1] for description. Note that this1821 setting is not subject to the 'identity' mechanism.18221823sendemail.smtpssl::1824 Deprecated alias for 'sendemail.smtpencryption = ssl'.18251826sendemail.<identity>.*::1827 Identity-specific versions of the 'sendemail.*' parameters1828 found below, taking precedence over those when the this1829 identity is selected, through command-line or1830 'sendemail.identity'.18311832sendemail.aliasesfile::1833sendemail.aliasfiletype::1834sendemail.bcc::1835sendemail.cc::1836sendemail.cccmd::1837sendemail.chainreplyto::1838sendemail.confirm::1839sendemail.envelopesender::1840sendemail.from::1841sendemail.multiedit::1842sendemail.signedoffbycc::1843sendemail.smtppass::1844sendemail.suppresscc::1845sendemail.suppressfrom::1846sendemail.to::1847sendemail.smtpdomain::1848sendemail.smtpserver::1849sendemail.smtpserverport::1850sendemail.smtpserveroption::1851sendemail.smtpuser::1852sendemail.thread::1853sendemail.validate::1854 See linkgit:git-send-email[1] for description.18551856sendemail.signedoffcc::1857 Deprecated alias for 'sendemail.signedoffbycc'.18581859showbranch.default::1860 The default set of branches for linkgit:git-show-branch[1].1861 See linkgit:git-show-branch[1].18621863status.relativePaths::1864 By default, linkgit:git-status[1] shows paths relative to the1865 current directory. Setting this variable to `false` shows paths1866 relative to the repository root (this was the default for git1867 prior to v1.5.4).18681869status.showUntrackedFiles::1870 By default, linkgit:git-status[1] and linkgit:git-commit[1] show1871 files which are not currently tracked by Git. Directories which1872 contain only untracked files, are shown with the directory name1873 only. Showing untracked files means that Git needs to lstat() all1874 all the files in the whole repository, which might be slow on some1875 systems. So, this variable controls how the commands displays1876 the untracked files. Possible values are:1877+1878--1879* `no` - Show no untracked files.1880* `normal` - Show untracked files and directories.1881* `all` - Show also individual files in untracked directories.1882--1883+1884If this variable is not specified, it defaults to 'normal'.1885This variable can be overridden with the -u|--untracked-files option1886of linkgit:git-status[1] and linkgit:git-commit[1].18871888status.submodulesummary::1889 Defaults to false.1890 If this is set to a non zero number or true (identical to -1 or an1891 unlimited number), the submodule summary will be enabled and a1892 summary of commits for modified submodules will be shown (see1893 --summary-limit option of linkgit:git-submodule[1]).18941895submodule.<name>.path::1896submodule.<name>.url::1897submodule.<name>.update::1898 The path within this project, URL, and the updating strategy1899 for a submodule. These variables are initially populated1900 by 'git submodule init'; edit them to override the1901 URL and other values found in the `.gitmodules` file. See1902 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.19031904submodule.<name>.fetchRecurseSubmodules::1905 This option can be used to control recursive fetching of this1906 submodule. It can be overridden by using the --[no-]recurse-submodules1907 command line option to "git fetch" and "git pull".1908 This setting will override that from in the linkgit:gitmodules[5]1909 file.19101911submodule.<name>.ignore::1912 Defines under what circumstances "git status" and the diff family show1913 a submodule as modified. When set to "all", it will never be considered1914 modified, "dirty" will ignore all changes to the submodules work tree and1915 takes only differences between the HEAD of the submodule and the commit1916 recorded in the superproject into account. "untracked" will additionally1917 let submodules with modified tracked files in their work tree show up.1918 Using "none" (the default when this option is not set) also shows1919 submodules that have untracked files in their work tree as changed.1920 This setting overrides any setting made in .gitmodules for this submodule,1921 both settings can be overridden on the command line by using the1922 "--ignore-submodules" option.19231924tar.umask::1925 This variable can be used to restrict the permission bits of1926 tar archive entries. The default is 0002, which turns off the1927 world write bit. The special value "user" indicates that the1928 archiving user's umask will be used instead. See umask(2) and1929 linkgit:git-archive[1].19301931transfer.fsckObjects::1932 When `fetch.fsckObjects` or `receive.fsckObjects` are1933 not set, the value of this variable is used instead.1934 Defaults to false.19351936transfer.unpackLimit::1937 When `fetch.unpackLimit` or `receive.unpackLimit` are1938 not set, the value of this variable is used instead.1939 The default value is 100.19401941url.<base>.insteadOf::1942 Any URL that starts with this value will be rewritten to1943 start, instead, with <base>. In cases where some site serves a1944 large number of repositories, and serves them with multiple1945 access methods, and some users need to use different access1946 methods, this feature allows people to specify any of the1947 equivalent URLs and have git automatically rewrite the URL to1948 the best alternative for the particular user, even for a1949 never-before-seen repository on the site. When more than one1950 insteadOf strings match a given URL, the longest match is used.19511952url.<base>.pushInsteadOf::1953 Any URL that starts with this value will not be pushed to;1954 instead, it will be rewritten to start with <base>, and the1955 resulting URL will be pushed to. In cases where some site serves1956 a large number of repositories, and serves them with multiple1957 access methods, some of which do not allow push, this feature1958 allows people to specify a pull-only URL and have git1959 automatically use an appropriate URL to push, even for a1960 never-before-seen repository on the site. When more than one1961 pushInsteadOf strings match a given URL, the longest match is1962 used. If a remote has an explicit pushurl, git will ignore this1963 setting for that remote.19641965user.email::1966 Your email address to be recorded in any newly created commits.1967 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and1968 'EMAIL' environment variables. See linkgit:git-commit-tree[1].19691970user.name::1971 Your full name to be recorded in any newly created commits.1972 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'1973 environment variables. See linkgit:git-commit-tree[1].19741975user.signingkey::1976 If linkgit:git-tag[1] is not selecting the key you want it to1977 automatically when creating a signed tag, you can override the1978 default selection with this variable. This option is passed1979 unchanged to gpg's --local-user parameter, so you may specify a key1980 using any method that gpg supports.19811982web.browser::1983 Specify a web browser that may be used by some commands.1984 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]1985 may use it.