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 deprecated `[section.subsection]` syntax. With this 49syntax, the subsection name is converted to lower-case and is also 50compared case sensitively. These subsection names follow the same 51restrictions as section names. 52 53All the other lines (and the remainder of the line after the section 54header) are recognized as setting variables, in the form 55'name = value'. If there is no equal sign on the line, the entire line 56is taken as 'name' and the variable is recognized as boolean "true". 57The variable names are case-insensitive and only alphanumeric 58characters and `-` are allowed. There can be more than one value 59for a given variable; we say then that variable is multivalued. 60 61Leading and trailing whitespace in a variable value is discarded. 62Internal whitespace within a variable value is retained verbatim. 63 64The values following the equals sign in variable assign are all either 65a string, an integer, or a boolean. Boolean values may be given as yes/no, 661/0, true/false or on/off. Case is not significant in boolean values, when 67converting value to the canonical form using '--bool' type specifier; 68'git config' will ensure that the output is "true" or "false". 69 70String values may be entirely or partially enclosed in double quotes. 71You need to enclose variable values in double quotes if you want to 72preserve leading or trailing whitespace, or if the variable value contains 73comment characters (i.e. it contains '#' or ';'). 74Double quote `"` and backslash `\` characters in variable values must 75be escaped: use `\"` for `"` and `\\` for `\`. 76 77The following escape sequences (beside `\"` and `\\`) are recognized: 78`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB) 79and `\b` for backspace (BS). No other char escape sequence, nor octal 80char sequences are valid. 81 82Variable values ending in a `\` are continued on the next line in the 83customary UNIX fashion. 84 85Some variables may require a special value format. 86 87Example 88~~~~~~~ 89 90 # Core variables 91 [core] 92 ; Don't trust file modes 93 filemode = false 94 95 # Our diff algorithm 96 [diff] 97 external = /usr/local/bin/diff-wrapper 98 renames = true 99 100 [branch "devel"] 101 remote = origin 102 merge = refs/heads/devel 103 104 # Proxy settings 105 [core] 106 gitProxy="ssh" for "kernel.org" 107 gitProxy=default-proxy ; for the rest 108 109Variables 110~~~~~~~~~ 111 112Note that this list is non-comprehensive and not necessarily complete. 113For command-specific variables, you will find a more detailed description 114in the appropriate manual page. You will find a description of non-core 115porcelain configuration variables in the respective porcelain documentation. 116 117advice.*:: 118 These variables control various optional help messages designed to 119 aid new users. All 'advice.*' variables default to 'true', and you 120 can tell Git that you do not need help by setting these to 'false': 121+ 122-- 123 pushNonFastForward:: 124 Advice shown when linkgit:git-push[1] refuses 125 non-fast-forward refs. 126 statusHints:: 127 Directions on how to stage/unstage/add shown in the 128 output of linkgit:git-status[1] and the template shown 129 when writing commit messages. 130 commitBeforeMerge:: 131 Advice shown when linkgit:git-merge[1] refuses to 132 merge to avoid overwriting local changes. 133 resolveConflict:: 134 Advices shown by various commands when conflicts 135 prevent the operation from being performed. 136 implicitIdentity:: 137 Advice on how to set your identity configuration when 138 your information is guessed from the system username and 139 domain name. 140 detachedHead:: 141 Advice shown when you used linkgit:git-checkout[1] to 142 move to the detach HEAD state, to instruct how to create 143 a local branch after the fact. 144-- 145 146core.fileMode:: 147 If false, the executable bit differences between the index and 148 the working tree are ignored; useful on broken filesystems like FAT. 149 See linkgit:git-update-index[1]. 150+ 151The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 152will probe and set core.fileMode false if appropriate when the 153repository is created. 154 155core.ignoreCygwinFSTricks:: 156 This option is only used by Cygwin implementation of Git. If false, 157 the Cygwin stat() and lstat() functions are used. This may be useful 158 if your repository consists of a few separate directories joined in 159 one hierarchy using Cygwin mount. If true, Git uses native Win32 API 160 whenever it is possible and falls back to Cygwin functions only to 161 handle symbol links. The native mode is more than twice faster than 162 normal Cygwin l/stat() functions. True by default, unless core.filemode 163 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's 164 POSIX emulation is required to support core.filemode. 165 166core.ignorecase:: 167 If true, this option enables various workarounds to enable 168 git to work better on filesystems that are not case sensitive, 169 like FAT. For example, if a directory listing finds 170 "makefile" when git expects "Makefile", git will assume 171 it is really the same file, and continue to remember it as 172 "Makefile". 173+ 174The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 175will probe and set core.ignorecase true if appropriate when the repository 176is created. 177 178core.trustctime:: 179 If false, the ctime differences between the index and the 180 working tree are ignored; useful when the inode change time 181 is regularly modified by something outside Git (file system 182 crawlers and some backup systems). 183 See linkgit:git-update-index[1]. True by default. 184 185core.quotepath:: 186 The commands that output paths (e.g. 'ls-files', 187 'diff'), when not given the `-z` option, will quote 188 "unusual" characters in the pathname by enclosing the 189 pathname in a double-quote pair and with backslashes the 190 same way strings in C source code are quoted. If this 191 variable is set to false, the bytes higher than 0x80 are 192 not quoted but output as verbatim. Note that double 193 quote, backslash and control characters are always 194 quoted without `-z` regardless of the setting of this 195 variable. 196 197core.eol:: 198 Sets the line ending type to use in the working directory for 199 files that have the `text` property set. Alternatives are 200 'lf', 'crlf' and 'native', which uses the platform's native 201 line ending. The default value is `native`. See 202 linkgit:gitattributes[5] for more information on end-of-line 203 conversion. 204 205core.safecrlf:: 206 If true, makes git check if converting `CRLF` is reversible when 207 end-of-line conversion is active. Git will verify if a command 208 modifies a file in the work tree either directly or indirectly. 209 For example, committing a file followed by checking out the 210 same file should yield the original file in the work tree. If 211 this is not the case for the current setting of 212 `core.autocrlf`, git will reject the file. The variable can 213 be set to "warn", in which case git will only warn about an 214 irreversible conversion but continue the operation. 215+ 216CRLF conversion bears a slight chance of corrupting data. 217When it is enabled, git will convert CRLF to LF during commit and LF to 218CRLF during checkout. A file that contains a mixture of LF and 219CRLF before the commit cannot be recreated by git. For text 220files this is the right thing to do: it corrects line endings 221such that we have only LF line endings in the repository. 222But for binary files that are accidentally classified as text the 223conversion can corrupt data. 224+ 225If you recognize such corruption early you can easily fix it by 226setting the conversion type explicitly in .gitattributes. Right 227after committing you still have the original file in your work 228tree and this file is not yet corrupted. You can explicitly tell 229git that this file is binary and git will handle the file 230appropriately. 231+ 232Unfortunately, the desired effect of cleaning up text files with 233mixed line endings and the undesired effect of corrupting binary 234files cannot be distinguished. In both cases CRLFs are removed 235in an irreversible way. For text files this is the right thing 236to do because CRLFs are line endings, while for binary files 237converting CRLFs corrupts data. 238+ 239Note, this safety check does not mean that a checkout will generate a 240file identical to the original file for a different setting of 241`core.eol` and `core.autocrlf`, but only for the current one. For 242example, a text file with `LF` would be accepted with `core.eol=lf` 243and could later be checked out with `core.eol=crlf`, in which case the 244resulting file would contain `CRLF`, although the original file 245contained `LF`. However, in both work trees the line endings would be 246consistent, that is either all `LF` or all `CRLF`, but never mixed. A 247file with mixed line endings would be reported by the `core.safecrlf` 248mechanism. 249 250core.autocrlf:: 251 Setting this variable to "true" is almost the same as setting 252 the `text` attribute to "auto" on all files except that text 253 files are not guaranteed to be normalized: files that contain 254 `CRLF` in the repository will not be touched. Use this 255 setting if you want to have `CRLF` line endings in your 256 working directory even though the repository does not have 257 normalized line endings. This variable can be set to 'input', 258 in which case no output conversion is performed. 259 260core.symlinks:: 261 If false, symbolic links are checked out as small plain files that 262 contain the link text. linkgit:git-update-index[1] and 263 linkgit:git-add[1] will not change the recorded type to regular 264 file. Useful on filesystems like FAT that do not support 265 symbolic links. 266+ 267The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 268will probe and set core.symlinks false if appropriate when the repository 269is created. 270 271core.gitProxy:: 272 A "proxy command" to execute (as 'command host port') instead 273 of establishing direct connection to the remote server when 274 using the git protocol for fetching. If the variable value is 275 in the "COMMAND for DOMAIN" format, the command is applied only 276 on hostnames ending with the specified domain string. This variable 277 may be set multiple times and is matched in the given order; 278 the first match wins. 279+ 280Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 281(which always applies universally, without the special "for" 282handling). 283+ 284The special string `none` can be used as the proxy command to 285specify that no proxy be used for a given domain pattern. 286This is useful for excluding servers inside a firewall from 287proxy use, while defaulting to a common proxy for external domains. 288 289core.ignoreStat:: 290 If true, commands which modify both the working tree and the index 291 will mark the updated paths with the "assume unchanged" bit in the 292 index. These marked files are then assumed to stay unchanged in the 293 working tree, until you mark them otherwise manually - Git will not 294 detect the file changes by lstat() calls. This is useful on systems 295 where those are very slow, such as Microsoft Windows. 296 See linkgit:git-update-index[1]. 297 False by default. 298 299core.preferSymlinkRefs:: 300 Instead of the default "symref" format for HEAD 301 and other symbolic reference files, use symbolic links. 302 This is sometimes needed to work with old scripts that 303 expect HEAD to be a symbolic link. 304 305core.bare:: 306 If true this repository is assumed to be 'bare' and has no 307 working directory associated with it. If this is the case a 308 number of commands that require a working directory will be 309 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 310+ 311This setting is automatically guessed by linkgit:git-clone[1] or 312linkgit:git-init[1] when the repository was created. By default a 313repository that ends in "/.git" is assumed to be not bare (bare = 314false), while all other repositories are assumed to be bare (bare 315= true). 316 317core.worktree:: 318 Set the path to the root of the working tree. 319 This can be overridden by the GIT_WORK_TREE environment 320 variable and the '--work-tree' command line option. 321 The value can be an absolute path or relative to the path to 322 the .git directory, which is either specified by --git-dir 323 or GIT_DIR, or automatically discovered. 324 If --git-dir or GIT_DIR is specified but none of 325 --work-tree, GIT_WORK_TREE and core.worktree is specified, 326 the current working directory is regarded as the top level 327 of your working tree. 328+ 329Note that this variable is honored even when set in a configuration 330file in a ".git" subdirectory of a directory and its value differs 331from the latter directory (e.g. "/path/to/.git/config" has 332core.worktree set to "/different/path"), which is most likely a 333misconfiguration. Running git commands in the "/path/to" directory will 334still use "/different/path" as the root of the work tree and can cause 335confusion unless you know what you are doing (e.g. you are creating a 336read-only snapshot of the same index to a location different from the 337repository's usual working tree). 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 (i.e. under 346 refs/heads/), remote refs (i.e. under refs/remotes/), 347 note refs (i.e. under refs/notes/), and the symbolic ref HEAD. 348+ 349This information can be used to determine what commit 350was the tip of a branch "2 days ago". 351+ 352This value is true by default in a repository that has 353a working directory associated with it, and false by 354default in a bare repository. 355 356core.repositoryFormatVersion:: 357 Internal variable identifying the repository format and layout 358 version. 359 360core.sharedRepository:: 361 When 'group' (or 'true'), the repository is made shareable between 362 several users in a group (making sure all the files and objects are 363 group-writable). When 'all' (or 'world' or 'everybody'), the 364 repository will be readable by all users, additionally to being 365 group-shareable. When 'umask' (or 'false'), git will use permissions 366 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 367 files in the repository will have this mode value. '0xxx' will override 368 user's umask value (whereas the other options will only override 369 requested parts of the user's umask value). Examples: '0660' will make 370 the repo read/write-able for the owner and group, but inaccessible to 371 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 372 repository that is group-readable but not group-writable. 373 See linkgit:git-init[1]. False by default. 374 375core.warnAmbiguousRefs:: 376 If true, git will warn you if the ref name you passed it is ambiguous 377 and might match multiple refs in the .git/refs/ tree. True by default. 378 379core.compression:: 380 An integer -1..9, indicating a default compression level. 381 -1 is the zlib default. 0 means no compression, 382 and 1..9 are various speed/size tradeoffs, 9 being slowest. 383 If set, this provides a default to other compression variables, 384 such as 'core.loosecompression' and 'pack.compression'. 385 386core.loosecompression:: 387 An integer -1..9, indicating the compression level for objects that 388 are not in a pack file. -1 is the zlib default. 0 means no 389 compression, and 1..9 are various speed/size tradeoffs, 9 being 390 slowest. If not set, defaults to core.compression. If that is 391 not set, defaults to 1 (best speed). 392 393core.packedGitWindowSize:: 394 Number of bytes of a pack file to map into memory in a 395 single mapping operation. Larger window sizes may allow 396 your system to process a smaller number of large pack files 397 more quickly. Smaller window sizes will negatively affect 398 performance due to increased calls to the operating system's 399 memory manager, but may improve performance when accessing 400 a large number of large pack files. 401+ 402Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 403MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 404be reasonable for all users/operating systems. You probably do 405not need to adjust this value. 406+ 407Common unit suffixes of 'k', 'm', or 'g' are supported. 408 409core.packedGitLimit:: 410 Maximum number of bytes to map simultaneously into memory 411 from pack files. If Git needs to access more than this many 412 bytes at once to complete an operation it will unmap existing 413 regions to reclaim virtual address space within the process. 414+ 415Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 416This should be reasonable for all users/operating systems, except on 417the largest projects. You probably do not need to adjust this value. 418+ 419Common unit suffixes of 'k', 'm', or 'g' are supported. 420 421core.deltaBaseCacheLimit:: 422 Maximum number of bytes to reserve for caching base objects 423 that may be referenced by multiple deltified objects. By storing the 424 entire decompressed base objects in a cache Git is able 425 to avoid unpacking and decompressing frequently used base 426 objects multiple times. 427+ 428Default is 16 MiB on all platforms. This should be reasonable 429for all users/operating systems, except on the largest projects. 430You probably do not need to adjust this value. 431+ 432Common unit suffixes of 'k', 'm', or 'g' are supported. 433 434core.bigFileThreshold:: 435 Files larger than this size are stored deflated, without 436 attempting delta compression. Storing large files without 437 delta compression avoids excessive memory usage, at the 438 slight expense of increased disk usage. 439+ 440Default is 512 MiB on all platforms. This should be reasonable 441for most projects as source code and other text files can still 442be delta compressed, but larger binary media files won't be. 443+ 444Common unit suffixes of 'k', 'm', or 'g' are supported. 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.askpass:: 454 Some commands (e.g. svn and http interfaces) that interactively 455 ask for a password can be told to use an external program given 456 via the value of this variable. Can be overridden by the 'GIT_ASKPASS' 457 environment variable. If not set, fall back to the value of the 458 'SSH_ASKPASS' environment variable or, failing that, a simple password 459 prompt. The external program shall be given a suitable prompt as 460 command line argument and write the password on its STDOUT. 461 462core.attributesfile:: 463 In addition to '.gitattributes' (per-directory) and 464 '.git/info/attributes', git looks into this file for attributes 465 (see linkgit:gitattributes[5]). Path expansions are made the same 466 way as for `core.excludesfile`. 467 468core.editor:: 469 Commands such as `commit` and `tag` that lets you edit 470 messages by launching an editor uses the value of this 471 variable when it is set, and the environment variable 472 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 473 474sequence.editor:: 475 Text editor used by `git rebase -i` for editing the rebase insn file. 476 The value is meant to be interpreted by the shell when it is used. 477 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 478 When not configured the default commit message editor is used instead. 479 480core.pager:: 481 The command that git will use to paginate output. Can 482 be overridden with the `GIT_PAGER` environment 483 variable. Note that git sets the `LESS` environment 484 variable to `FRSX` if it is unset when it runs the 485 pager. One can change these settings by setting the 486 `LESS` variable to some other value. Alternately, 487 these settings can be overridden on a project or 488 global basis by setting the `core.pager` option. 489 Setting `core.pager` has no affect on the `LESS` 490 environment variable behaviour above, so if you want 491 to override git's default settings this way, you need 492 to be explicit. For example, to disable the S option 493 in a backward compatible manner, set `core.pager` 494 to `less -+$LESS -FRX`. This will be passed to the 495 shell by git, which will translate the final command to 496 `LESS=FRSX less -+FRSX -FRX`. 497 498core.whitespace:: 499 A comma separated list of common whitespace problems to 500 notice. 'git diff' will use `color.diff.whitespace` to 501 highlight them, and 'git apply --whitespace=error' will 502 consider them as errors. You can prefix `-` to disable 503 any of them (e.g. `-trailing-space`): 504+ 505* `blank-at-eol` treats trailing whitespaces at the end of the line 506 as an error (enabled by default). 507* `space-before-tab` treats a space character that appears immediately 508 before a tab character in the initial indent part of the line as an 509 error (enabled by default). 510* `indent-with-non-tab` treats a line that is indented with 8 or more 511 space characters as an error (not enabled by default). 512* `tab-in-indent` treats a tab character in the initial indent part of 513 the line as an error (not enabled by default). 514* `blank-at-eof` treats blank lines added at the end of file as an error 515 (enabled by default). 516* `trailing-space` is a short-hand to cover both `blank-at-eol` and 517 `blank-at-eof`. 518* `cr-at-eol` treats a carriage-return at the end of line as 519 part of the line terminator, i.e. with it, `trailing-space` 520 does not trigger if the character before such a carriage-return 521 is not a whitespace (not enabled by default). 522* `tabwidth=<n>` tells how many character positions a tab occupies; this 523 is relevant for `indent-with-non-tab` and when git fixes `tab-in-indent` 524 errors. The default tab width is 8. Allowed values are 1 to 63. 525 526core.fsyncobjectfiles:: 527 This boolean will enable 'fsync()' when writing object files. 528+ 529This is a total waste of time and effort on a filesystem that orders 530data writes properly, but can be useful for filesystems that do not use 531journalling (traditional UNIX filesystems) or that only journal metadata 532and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 533 534core.preloadindex:: 535 Enable parallel index preload for operations like 'git diff' 536+ 537This can speed up operations like 'git diff' and 'git status' especially 538on filesystems like NFS that have weak caching semantics and thus 539relatively high IO latencies. With this set to 'true', git will do the 540index comparison to the filesystem data in parallel, allowing 541overlapping IO's. 542 543core.createObject:: 544 You can set this to 'link', in which case a hardlink followed by 545 a delete of the source are used to make sure that object creation 546 will not overwrite existing objects. 547+ 548On some file system/operating system combinations, this is unreliable. 549Set this config setting to 'rename' there; However, This will remove the 550check that makes sure that existing object files will not get overwritten. 551 552core.notesRef:: 553 When showing commit messages, also show notes which are stored in 554 the given ref. The ref must be fully qualified. If the given 555 ref does not exist, it is not an error but means that no 556 notes should be printed. 557+ 558This setting defaults to "refs/notes/commits", and it can be overridden by 559the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1]. 560 561core.sparseCheckout:: 562 Enable "sparse checkout" feature. See section "Sparse checkout" in 563 linkgit:git-read-tree[1] for more information. 564 565core.abbrev:: 566 Set the length object names are abbreviated to. If unspecified, 567 many commands abbreviate to 7 hexdigits, which may not be enough 568 for abbreviated object names to stay unique for sufficiently long 569 time. 570 571add.ignore-errors:: 572add.ignoreErrors:: 573 Tells 'git add' to continue adding files when some files cannot be 574 added due to indexing errors. Equivalent to the '--ignore-errors' 575 option of linkgit:git-add[1]. Older versions of git accept only 576 `add.ignore-errors`, which does not follow the usual naming 577 convention for configuration variables. Newer versions of git 578 honor `add.ignoreErrors` as well. 579 580alias.*:: 581 Command aliases for the linkgit:git[1] command wrapper - e.g. 582 after defining "alias.last = cat-file commit HEAD", the invocation 583 "git last" is equivalent to "git cat-file commit HEAD". To avoid 584 confusion and troubles with script usage, aliases that 585 hide existing git commands are ignored. Arguments are split by 586 spaces, the usual shell quoting and escaping is supported. 587 quote pair and a backslash can be used to quote them. 588+ 589If the alias expansion is prefixed with an exclamation point, 590it will be treated as a shell command. For example, defining 591"alias.new = !gitk --all --not ORIG_HEAD", the invocation 592"git new" is equivalent to running the shell command 593"gitk --all --not ORIG_HEAD". Note that shell commands will be 594executed from the top-level directory of a repository, which may 595not necessarily be the current directory. 596'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix' 597from the original current directory. See linkgit:git-rev-parse[1]. 598 599am.keepcr:: 600 If true, git-am will call git-mailsplit for patches in mbox format 601 with parameter '--keep-cr'. In this case git-mailsplit will 602 not remove `\r` from lines ending with `\r\n`. Can be overridden 603 by giving '--no-keep-cr' from the command line. 604 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 605 606apply.ignorewhitespace:: 607 When set to 'change', tells 'git apply' to ignore changes in 608 whitespace, in the same way as the '--ignore-space-change' 609 option. 610 When set to one of: no, none, never, false tells 'git apply' to 611 respect all whitespace differences. 612 See linkgit:git-apply[1]. 613 614apply.whitespace:: 615 Tells 'git apply' how to handle whitespaces, in the same way 616 as the '--whitespace' option. See linkgit:git-apply[1]. 617 618branch.autosetupmerge:: 619 Tells 'git branch' and 'git checkout' to set up new branches 620 so that linkgit:git-pull[1] will appropriately merge from the 621 starting point branch. Note that even if this option is not set, 622 this behavior can be chosen per-branch using the `--track` 623 and `--no-track` options. The valid settings are: `false` -- no 624 automatic setup is done; `true` -- automatic setup is done when the 625 starting point is a remote-tracking branch; `always` -- 626 automatic setup is done when the starting point is either a 627 local branch or remote-tracking 628 branch. This option defaults to true. 629 630branch.autosetuprebase:: 631 When a new branch is created with 'git branch' or 'git checkout' 632 that tracks another branch, this variable tells git to set 633 up pull to rebase instead of merge (see "branch.<name>.rebase"). 634 When `never`, rebase is never automatically set to true. 635 When `local`, rebase is set to true for tracked branches of 636 other local branches. 637 When `remote`, rebase is set to true for tracked branches of 638 remote-tracking branches. 639 When `always`, rebase will be set to true for all tracking 640 branches. 641 See "branch.autosetupmerge" for details on how to set up a 642 branch to track another branch. 643 This option defaults to never. 644 645branch.<name>.remote:: 646 When in branch <name>, it tells 'git fetch' and 'git push' which 647 remote to fetch from/push to. It defaults to `origin` if no remote is 648 configured. `origin` is also used if you are not on any branch. 649 650branch.<name>.merge:: 651 Defines, together with branch.<name>.remote, the upstream branch 652 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which 653 branch to merge and can also affect 'git push' (see push.default). 654 When in branch <name>, it tells 'git fetch' the default 655 refspec to be marked for merging in FETCH_HEAD. The value is 656 handled like the remote part of a refspec, and must match a 657 ref which is fetched from the remote given by 658 "branch.<name>.remote". 659 The merge information is used by 'git pull' (which at first calls 660 'git fetch') to lookup the default branch for merging. Without 661 this option, 'git pull' defaults to merge the first refspec fetched. 662 Specify multiple values to get an octopus merge. 663 If you wish to setup 'git pull' so that it merges into <name> from 664 another branch in the local repository, you can point 665 branch.<name>.merge to the desired branch, and use the special setting 666 `.` (a period) for branch.<name>.remote. 667 668branch.<name>.mergeoptions:: 669 Sets default options for merging into branch <name>. The syntax and 670 supported options are the same as those of linkgit:git-merge[1], but 671 option values containing whitespace characters are currently not 672 supported. 673 674branch.<name>.rebase:: 675 When true, rebase the branch <name> on top of the fetched branch, 676 instead of merging the default branch from the default remote when 677 "git pull" is run. See "pull.rebase" for doing this in a non 678 branch-specific manner. 679+ 680*NOTE*: this is a possibly dangerous operation; do *not* use 681it unless you understand the implications (see linkgit:git-rebase[1] 682for details). 683 684browser.<tool>.cmd:: 685 Specify the command to invoke the specified browser. The 686 specified command is evaluated in shell with the URLs passed 687 as arguments. (See linkgit:git-web{litdd}browse[1].) 688 689browser.<tool>.path:: 690 Override the path for the given tool that may be used to 691 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 692 working repository in gitweb (see linkgit:git-instaweb[1]). 693 694clean.requireForce:: 695 A boolean to make git-clean do nothing unless given -f 696 or -n. Defaults to true. 697 698color.branch:: 699 A boolean to enable/disable color in the output of 700 linkgit:git-branch[1]. May be set to `always`, 701 `false` (or `never`) or `auto` (or `true`), in which case colors are used 702 only when the output is to a terminal. Defaults to false. 703 704color.branch.<slot>:: 705 Use customized color for branch coloration. `<slot>` is one of 706 `current` (the current branch), `local` (a local branch), 707 `remote` (a remote-tracking branch in refs/remotes/), `plain` (other 708 refs). 709+ 710The value for these configuration variables is a list of colors (at most 711two) and attributes (at most one), separated by spaces. The colors 712accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`, 713`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`, 714`blink` and `reverse`. The first color given is the foreground; the 715second is the background. The position of the attribute, if any, 716doesn't matter. 717 718color.diff:: 719 Whether to use ANSI escape sequences to add color to patches. 720 If this is set to `always`, linkgit:git-diff[1], 721 linkgit:git-log[1], and linkgit:git-show[1] will use color 722 for all patches. If it is set to `true` or `auto`, those 723 commands will only use color when output is to the terminal. 724 Defaults to false. 725+ 726This does not affect linkgit:git-format-patch[1] nor the 727'git-diff-{asterisk}' plumbing commands. Can be overridden on the 728command line with the `--color[=<when>]` option. 729 730color.diff.<slot>:: 731 Use customized color for diff colorization. `<slot>` specifies 732 which part of the patch to use the specified color, and is one 733 of `plain` (context text), `meta` (metainformation), `frag` 734 (hunk header), 'func' (function in hunk header), `old` (removed lines), 735 `new` (added lines), `commit` (commit headers), or `whitespace` 736 (highlighting whitespace errors). The values of these variables may be 737 specified as in color.branch.<slot>. 738 739color.decorate.<slot>:: 740 Use customized color for 'git log --decorate' output. `<slot>` is one 741 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local 742 branches, remote-tracking branches, tags, stash and HEAD, respectively. 743 744color.grep:: 745 When set to `always`, always highlight matches. When `false` (or 746 `never`), never. When set to `true` or `auto`, use color only 747 when the output is written to the terminal. Defaults to `false`. 748 749color.grep.<slot>:: 750 Use customized color for grep colorization. `<slot>` specifies which 751 part of the line to use the specified color, and is one of 752+ 753-- 754`context`;; 755 non-matching text in context lines (when using `-A`, `-B`, or `-C`) 756`filename`;; 757 filename prefix (when not using `-h`) 758`function`;; 759 function name lines (when using `-p`) 760`linenumber`;; 761 line number prefix (when using `-n`) 762`match`;; 763 matching text 764`selected`;; 765 non-matching text in selected lines 766`separator`;; 767 separators between fields on a line (`:`, `-`, and `=`) 768 and between hunks (`--`) 769-- 770+ 771The values of these variables may be specified as in color.branch.<slot>. 772 773color.interactive:: 774 When set to `always`, always use colors for interactive prompts 775 and displays (such as those used by "git-add --interactive"). 776 When false (or `never`), never. When set to `true` or `auto`, use 777 colors only when the output is to the terminal. Defaults to false. 778 779color.interactive.<slot>:: 780 Use customized color for 'git add --interactive' 781 output. `<slot>` may be `prompt`, `header`, `help` or `error`, for 782 four distinct types of normal output from interactive 783 commands. The values of these variables may be specified as 784 in color.branch.<slot>. 785 786color.pager:: 787 A boolean to enable/disable colored output when the pager is in 788 use (default is true). 789 790color.showbranch:: 791 A boolean to enable/disable color in the output of 792 linkgit:git-show-branch[1]. May be set to `always`, 793 `false` (or `never`) or `auto` (or `true`), in which case colors are used 794 only when the output is to a terminal. Defaults to false. 795 796color.status:: 797 A boolean to enable/disable color in the output of 798 linkgit:git-status[1]. May be set to `always`, 799 `false` (or `never`) or `auto` (or `true`), in which case colors are used 800 only when the output is to a terminal. Defaults to false. 801 802color.status.<slot>:: 803 Use customized color for status colorization. `<slot>` is 804 one of `header` (the header text of the status message), 805 `added` or `updated` (files which are added but not committed), 806 `changed` (files which are changed but not added in the index), 807 `untracked` (files which are not tracked by git), 808 `branch` (the current branch), or 809 `nobranch` (the color the 'no branch' warning is shown in, defaulting 810 to red). The values of these variables may be specified as in 811 color.branch.<slot>. 812 813color.ui:: 814 This variable determines the default value for variables such 815 as `color.diff` and `color.grep` that control the use of color 816 per command family. Its scope will expand as more commands learn 817 configuration to set a default for the `--color` option. Set it 818 to `always` if you want all output not intended for machine 819 consumption to use color, to `true` or `auto` if you want such 820 output to use color when written to the terminal, or to `false` or 821 `never` if you prefer git commands not to use color unless enabled 822 explicitly with some other configuration or the `--color` option. 823 824commit.status:: 825 A boolean to enable/disable inclusion of status information in the 826 commit message template when using an editor to prepare the commit 827 message. Defaults to true. 828 829commit.template:: 830 Specify a file to use as the template for new commit messages. 831 "{tilde}/" is expanded to the value of `$HOME` and "{tilde}user/" to the 832 specified user's home directory. 833 834credential.helper:: 835 Specify an external helper to be called when a username or 836 password credential is needed; the helper may consult external 837 storage to avoid prompting the user for the credentials. See 838 linkgit:gitcredentials[7] for details. 839 840credential.useHttpPath:: 841 When acquiring credentials, consider the "path" component of an http 842 or https URL to be important. Defaults to false. See 843 linkgit:gitcredentials[7] for more information. 844 845credential.username:: 846 If no username is set for a network authentication, use this username 847 by default. See credential.<context>.* below, and 848 linkgit:gitcredentials[7]. 849 850credential.<url>.*:: 851 Any of the credential.* options above can be applied selectively to 852 some credentials. For example "credential.https://example.com.username" 853 would set the default username only for https connections to 854 example.com. See linkgit:gitcredentials[7] for details on how URLs are 855 matched. 856 857include::diff-config.txt[] 858 859difftool.<tool>.path:: 860 Override the path for the given tool. This is useful in case 861 your tool is not in the PATH. 862 863difftool.<tool>.cmd:: 864 Specify the command to invoke the specified diff tool. 865 The specified command is evaluated in shell with the following 866 variables available: 'LOCAL' is set to the name of the temporary 867 file containing the contents of the diff pre-image and 'REMOTE' 868 is set to the name of the temporary file containing the contents 869 of the diff post-image. 870 871difftool.prompt:: 872 Prompt before each invocation of the diff tool. 873 874diff.wordRegex:: 875 A POSIX Extended Regular Expression used to determine what is a "word" 876 when performing word-by-word difference calculations. Character 877 sequences that match the regular expression are "words", all other 878 characters are *ignorable* whitespace. 879 880fetch.recurseSubmodules:: 881 This option can be either set to a boolean value or to 'on-demand'. 882 Setting it to a boolean changes the behavior of fetch and pull to 883 unconditionally recurse into submodules when set to true or to not 884 recurse at all when set to false. When set to 'on-demand' (the default 885 value), fetch and pull will only recurse into a populated submodule 886 when its superproject retrieves a commit that updates the submodule's 887 reference. 888 889fetch.fsckObjects:: 890 If it is set to true, git-fetch-pack will check all fetched 891 objects. It will abort in the case of a malformed object or a 892 broken link. The result of an abort are only dangling objects. 893 Defaults to false. If not set, the value of `transfer.fsckObjects` 894 is used instead. 895 896fetch.unpackLimit:: 897 If the number of objects fetched over the git native 898 transfer is below this 899 limit, then the objects will be unpacked into loose object 900 files. However if the number of received objects equals or 901 exceeds this limit then the received pack will be stored as 902 a pack, after adding any missing delta bases. Storing the 903 pack from a push can make the push operation complete faster, 904 especially on slow filesystems. If not set, the value of 905 `transfer.unpackLimit` is used instead. 906 907format.attach:: 908 Enable multipart/mixed attachments as the default for 909 'format-patch'. The value can also be a double quoted string 910 which will enable attachments as the default and set the 911 value as the boundary. See the --attach option in 912 linkgit:git-format-patch[1]. 913 914format.numbered:: 915 A boolean which can enable or disable sequence numbers in patch 916 subjects. It defaults to "auto" which enables it only if there 917 is more than one patch. It can be enabled or disabled for all 918 messages by setting it to "true" or "false". See --numbered 919 option in linkgit:git-format-patch[1]. 920 921format.headers:: 922 Additional email headers to include in a patch to be submitted 923 by mail. See linkgit:git-format-patch[1]. 924 925format.to:: 926format.cc:: 927 Additional recipients to include in a patch to be submitted 928 by mail. See the --to and --cc options in 929 linkgit:git-format-patch[1]. 930 931format.subjectprefix:: 932 The default for format-patch is to output files with the '[PATCH]' 933 subject prefix. Use this variable to change that prefix. 934 935format.signature:: 936 The default for format-patch is to output a signature containing 937 the git version number. Use this variable to change that default. 938 Set this variable to the empty string ("") to suppress 939 signature generation. 940 941format.suffix:: 942 The default for format-patch is to output files with the suffix 943 `.patch`. Use this variable to change that suffix (make sure to 944 include the dot if you want it). 945 946format.pretty:: 947 The default pretty format for log/show/whatchanged command, 948 See linkgit:git-log[1], linkgit:git-show[1], 949 linkgit:git-whatchanged[1]. 950 951format.thread:: 952 The default threading style for 'git format-patch'. Can be 953 a boolean value, or `shallow` or `deep`. `shallow` threading 954 makes every mail a reply to the head of the series, 955 where the head is chosen from the cover letter, the 956 `\--in-reply-to`, and the first patch mail, in this order. 957 `deep` threading makes every mail a reply to the previous one. 958 A true boolean value is the same as `shallow`, and a false 959 value disables threading. 960 961format.signoff:: 962 A boolean value which lets you enable the `-s/--signoff` option of 963 format-patch by default. *Note:* Adding the Signed-off-by: line to a 964 patch should be a conscious act and means that you certify you have 965 the rights to submit this work under the same open source license. 966 Please see the 'SubmittingPatches' document for further discussion. 967 968filter.<driver>.clean:: 969 The command which is used to convert the content of a worktree 970 file to a blob upon checkin. See linkgit:gitattributes[5] for 971 details. 972 973filter.<driver>.smudge:: 974 The command which is used to convert the content of a blob 975 object to a worktree file upon checkout. See 976 linkgit:gitattributes[5] for details. 977 978gc.aggressiveWindow:: 979 The window size parameter used in the delta compression 980 algorithm used by 'git gc --aggressive'. This defaults 981 to 250. 982 983gc.auto:: 984 When there are approximately more than this many loose 985 objects in the repository, `git gc --auto` will pack them. 986 Some Porcelain commands use this command to perform a 987 light-weight garbage collection from time to time. The 988 default value is 6700. Setting this to 0 disables it. 989 990gc.autopacklimit:: 991 When there are more than this many packs that are not 992 marked with `*.keep` file in the repository, `git gc 993 --auto` consolidates them into one larger pack. The 994 default value is 50. Setting this to 0 disables it. 995 996gc.packrefs:: 997 Running `git pack-refs` in a repository renders it 998 unclonable by Git versions prior to 1.5.1.2 over dumb 999 transports such as HTTP. This variable determines whether1000 'git gc' runs `git pack-refs`. This can be set to `notbare`1001 to enable it within all non-bare repos or it can be set to a1002 boolean value. The default is `true`.10031004gc.pruneexpire::1005 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1006 Override the grace period with this config variable. The value1007 "now" may be used to disable this grace period and always prune1008 unreachable objects immediately.10091010gc.reflogexpire::1011gc.<pattern>.reflogexpire::1012 'git reflog expire' removes reflog entries older than1013 this time; defaults to 90 days. With "<pattern>" (e.g.1014 "refs/stash") in the middle the setting applies only to1015 the refs that match the <pattern>.10161017gc.reflogexpireunreachable::1018gc.<ref>.reflogexpireunreachable::1019 'git reflog expire' removes reflog entries older than1020 this time and are not reachable from the current tip;1021 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")1022 in the middle, the setting applies only to the refs that1023 match the <pattern>.10241025gc.rerereresolved::1026 Records of conflicted merge you resolved earlier are1027 kept for this many days when 'git rerere gc' is run.1028 The default is 60 days. See linkgit:git-rerere[1].10291030gc.rerereunresolved::1031 Records of conflicted merge you have not resolved are1032 kept for this many days when 'git rerere gc' is run.1033 The default is 15 days. See linkgit:git-rerere[1].10341035gitcvs.commitmsgannotation::1036 Append this string to each commit message. Set to empty string1037 to disable this feature. Defaults to "via git-CVS emulator".10381039gitcvs.enabled::1040 Whether the CVS server interface is enabled for this repository.1041 See linkgit:git-cvsserver[1].10421043gitcvs.logfile::1044 Path to a log file where the CVS server interface well... logs1045 various stuff. See linkgit:git-cvsserver[1].10461047gitcvs.usecrlfattr::1048 If true, the server will look up the end-of-line conversion1049 attributes for files to determine the '-k' modes to use. If1050 the attributes force git to treat a file as text,1051 the '-k' mode will be left blank so CVS clients will1052 treat it as text. If they suppress text conversion, the file1053 will be set with '-kb' mode, which suppresses any newline munging1054 the client might otherwise do. If the attributes do not allow1055 the file type to be determined, then 'gitcvs.allbinary' is1056 used. See linkgit:gitattributes[5].10571058gitcvs.allbinary::1059 This is used if 'gitcvs.usecrlfattr' does not resolve1060 the correct '-kb' mode to use. If true, all1061 unresolved files are sent to the client in1062 mode '-kb'. This causes the client to treat them1063 as binary files, which suppresses any newline munging it1064 otherwise might do. Alternatively, if it is set to "guess",1065 then the contents of the file are examined to decide if1066 it is binary, similar to 'core.autocrlf'.10671068gitcvs.dbname::1069 Database used by git-cvsserver to cache revision information1070 derived from the git repository. The exact meaning depends on the1071 used database driver, for SQLite (which is the default driver) this1072 is a filename. Supports variable substitution (see1073 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1074 Default: '%Ggitcvs.%m.sqlite'10751076gitcvs.dbdriver::1077 Used Perl DBI driver. You can specify any available driver1078 for this here, but it might not work. git-cvsserver is tested1079 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1080 reported *not* to work with 'DBD::mysql'. Experimental feature.1081 May not contain double colons (`:`). Default: 'SQLite'.1082 See linkgit:git-cvsserver[1].10831084gitcvs.dbuser, gitcvs.dbpass::1085 Database user and password. Only useful if setting 'gitcvs.dbdriver',1086 since SQLite has no concept of database users and/or passwords.1087 'gitcvs.dbuser' supports variable substitution (see1088 linkgit:git-cvsserver[1] for details).10891090gitcvs.dbTableNamePrefix::1091 Database table name prefix. Prepended to the names of any1092 database tables used, allowing a single database to be used1093 for several repositories. Supports variable substitution (see1094 linkgit:git-cvsserver[1] for details). Any non-alphabetic1095 characters will be replaced with underscores.10961097All gitcvs variables except for 'gitcvs.usecrlfattr' and1098'gitcvs.allbinary' can also be specified as1099'gitcvs.<access_method>.<varname>' (where 'access_method'1100is one of "ext" and "pserver") to make them apply only for the given1101access method.11021103gitweb.category::1104gitweb.description::1105gitweb.owner::1106gitweb.url::1107 See linkgit:gitweb[1] for description.11081109gitweb.avatar::1110gitweb.blame::1111gitweb.grep::1112gitweb.highlight::1113gitweb.patches::1114gitweb.pickaxe::1115gitweb.remote_heads::1116gitweb.showsizes::1117gitweb.snapshot::1118 See linkgit:gitweb.conf[5] for description.11191120grep.lineNumber::1121 If set to true, enable '-n' option by default.11221123grep.extendedRegexp::1124 If set to true, enable '--extended-regexp' option by default.11251126gui.commitmsgwidth::1127 Defines how wide the commit message window is in the1128 linkgit:git-gui[1]. "75" is the default.11291130gui.diffcontext::1131 Specifies how many context lines should be used in calls to diff1132 made by the linkgit:git-gui[1]. The default is "5".11331134gui.encoding::1135 Specifies the default encoding to use for displaying of1136 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1137 It can be overridden by setting the 'encoding' attribute1138 for relevant files (see linkgit:gitattributes[5]).1139 If this option is not set, the tools default to the1140 locale encoding.11411142gui.matchtrackingbranch::1143 Determines if new branches created with linkgit:git-gui[1] should1144 default to tracking remote branches with matching names or1145 not. Default: "false".11461147gui.newbranchtemplate::1148 Is used as suggested name when creating new branches using the1149 linkgit:git-gui[1].11501151gui.pruneduringfetch::1152 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1153 performing a fetch. The default value is "false".11541155gui.trustmtime::1156 Determines if linkgit:git-gui[1] should trust the file modification1157 timestamp or not. By default the timestamps are not trusted.11581159gui.spellingdictionary::1160 Specifies the dictionary used for spell checking commit messages in1161 the linkgit:git-gui[1]. When set to "none" spell checking is turned1162 off.11631164gui.fastcopyblame::1165 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1166 location detection. It makes blame significantly faster on huge1167 repositories at the expense of less thorough copy detection.11681169gui.copyblamethreshold::1170 Specifies the threshold to use in 'git gui blame' original location1171 detection, measured in alphanumeric characters. See the1172 linkgit:git-blame[1] manual for more information on copy detection.11731174gui.blamehistoryctx::1175 Specifies the radius of history context in days to show in1176 linkgit:gitk[1] for the selected commit, when the `Show History1177 Context` menu item is invoked from 'git gui blame'. If this1178 variable is set to zero, the whole history is shown.11791180guitool.<name>.cmd::1181 Specifies the shell command line to execute when the corresponding item1182 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1183 mandatory for every tool. The command is executed from the root of1184 the working directory, and in the environment it receives the name of1185 the tool as 'GIT_GUITOOL', the name of the currently selected file as1186 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1187 the head is detached, 'CUR_BRANCH' is empty).11881189guitool.<name>.needsfile::1190 Run the tool only if a diff is selected in the GUI. It guarantees1191 that 'FILENAME' is not empty.11921193guitool.<name>.noconsole::1194 Run the command silently, without creating a window to display its1195 output.11961197guitool.<name>.norescan::1198 Don't rescan the working directory for changes after the tool1199 finishes execution.12001201guitool.<name>.confirm::1202 Show a confirmation dialog before actually running the tool.12031204guitool.<name>.argprompt::1205 Request a string argument from the user, and pass it to the tool1206 through the 'ARGS' environment variable. Since requesting an1207 argument implies confirmation, the 'confirm' option has no effect1208 if this is enabled. If the option is set to 'true', 'yes', or '1',1209 the dialog uses a built-in generic prompt; otherwise the exact1210 value of the variable is used.12111212guitool.<name>.revprompt::1213 Request a single valid revision from the user, and set the1214 'REVISION' environment variable. In other aspects this option1215 is similar to 'argprompt', and can be used together with it.12161217guitool.<name>.revunmerged::1218 Show only unmerged branches in the 'revprompt' subdialog.1219 This is useful for tools similar to merge or rebase, but not1220 for things like checkout or reset.12211222guitool.<name>.title::1223 Specifies the title to use for the prompt dialog. The default1224 is the tool name.12251226guitool.<name>.prompt::1227 Specifies the general prompt string to display at the top of1228 the dialog, before subsections for 'argprompt' and 'revprompt'.1229 The default value includes the actual command.12301231help.browser::1232 Specify the browser that will be used to display help in the1233 'web' format. See linkgit:git-help[1].12341235help.format::1236 Override the default help format used by linkgit:git-help[1].1237 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1238 the default. 'web' and 'html' are the same.12391240help.autocorrect::1241 Automatically correct and execute mistyped commands after1242 waiting for the given number of deciseconds (0.1 sec). If more1243 than one command can be deduced from the entered text, nothing1244 will be executed. If the value of this option is negative,1245 the corrected command will be executed immediately. If the1246 value is 0 - the command will be just shown but not executed.1247 This is the default.12481249http.proxy::1250 Override the HTTP proxy, normally configured using the 'http_proxy'1251 environment variable (see linkgit:curl[1]). This can be overridden1252 on a per-remote basis; see remote.<name>.proxy12531254http.cookiefile::1255 File containing previously stored cookie lines which should be used1256 in the git http session, if they match the server. The file format1257 of the file to read cookies from should be plain HTTP headers or1258 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).1259 NOTE that the file specified with http.cookiefile is only used as1260 input. No cookies will be stored in the file.12611262http.sslVerify::1263 Whether to verify the SSL certificate when fetching or pushing1264 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1265 variable.12661267http.sslCert::1268 File containing the SSL certificate when fetching or pushing1269 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1270 variable.12711272http.sslKey::1273 File containing the SSL private key when fetching or pushing1274 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1275 variable.12761277http.sslCertPasswordProtected::1278 Enable git's password prompt for the SSL certificate. Otherwise1279 OpenSSL will prompt the user, possibly many times, if the1280 certificate or private key is encrypted. Can be overridden by the1281 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.12821283http.sslCAInfo::1284 File containing the certificates to verify the peer with when1285 fetching or pushing over HTTPS. Can be overridden by the1286 'GIT_SSL_CAINFO' environment variable.12871288http.sslCAPath::1289 Path containing files with the CA certificates to verify the peer1290 with when fetching or pushing over HTTPS. Can be overridden1291 by the 'GIT_SSL_CAPATH' environment variable.12921293http.maxRequests::1294 How many HTTP requests to launch in parallel. Can be overridden1295 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.12961297http.minSessions::1298 The number of curl sessions (counted across slots) to be kept across1299 requests. They will not be ended with curl_easy_cleanup() until1300 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1301 value will be capped at 1. Defaults to 1.13021303http.postBuffer::1304 Maximum size in bytes of the buffer used by smart HTTP1305 transports when POSTing data to the remote system.1306 For requests larger than this buffer size, HTTP/1.1 and1307 Transfer-Encoding: chunked is used to avoid creating a1308 massive pack file locally. Default is 1 MiB, which is1309 sufficient for most requests.13101311http.lowSpeedLimit, http.lowSpeedTime::1312 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1313 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1314 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1315 'GIT_HTTP_LOW_SPEED_TIME' environment variables.13161317http.noEPSV::1318 A boolean which disables using of EPSV ftp command by curl.1319 This can helpful with some "poor" ftp servers which don't1320 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1321 environment variable. Default is false (curl will use EPSV).13221323http.useragent::1324 The HTTP USER_AGENT string presented to an HTTP server. The default1325 value represents the version of the client git such as git/1.7.1.1326 This option allows you to override this value to a more common value1327 such as Mozilla/4.0. This may be necessary, for instance, if1328 connecting through a firewall that restricts HTTP connections to a set1329 of common USER_AGENT strings (but not including those like git/1.7.1).1330 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.13311332i18n.commitEncoding::1333 Character encoding the commit messages are stored in; git itself1334 does not care per se, but this information is necessary e.g. when1335 importing commits from emails or in the gitk graphical history1336 browser (and possibly at other places in the future or in other1337 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.13381339i18n.logOutputEncoding::1340 Character encoding the commit messages are converted to when1341 running 'git log' and friends.13421343imap::1344 The configuration variables in the 'imap' section are described1345 in linkgit:git-imap-send[1].13461347init.templatedir::1348 Specify the directory from which templates will be copied.1349 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)13501351instaweb.browser::1352 Specify the program that will be used to browse your working1353 repository in gitweb. See linkgit:git-instaweb[1].13541355instaweb.httpd::1356 The HTTP daemon command-line to start gitweb on your working1357 repository. See linkgit:git-instaweb[1].13581359instaweb.local::1360 If true the web server started by linkgit:git-instaweb[1] will1361 be bound to the local IP (127.0.0.1).13621363instaweb.modulepath::1364 The default module path for linkgit:git-instaweb[1] to use1365 instead of /usr/lib/apache2/modules. Only used if httpd1366 is Apache.13671368instaweb.port::1369 The port number to bind the gitweb httpd to. See1370 linkgit:git-instaweb[1].13711372interactive.singlekey::1373 In interactive commands, allow the user to provide one-letter1374 input with a single key (i.e., without hitting enter).1375 Currently this is used by the `\--patch` mode of1376 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],1377 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this1378 setting is silently ignored if portable keystroke input1379 is not available.13801381log.abbrevCommit::1382 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1383 linkgit:git-whatchanged[1] assume `\--abbrev-commit`. You may1384 override this option with `\--no-abbrev-commit`.13851386log.date::1387 Set the default date-time mode for the 'log' command.1388 Setting a value for log.date is similar to using 'git log''s1389 `\--date` option. Possible values are `relative`, `local`,1390 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]1391 for details.13921393log.decorate::1394 Print out the ref names of any commits that are shown by the log1395 command. If 'short' is specified, the ref name prefixes 'refs/heads/',1396 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is1397 specified, the full ref name (including prefix) will be printed.1398 This is the same as the log commands '--decorate' option.13991400log.showroot::1401 If true, the initial commit will be shown as a big creation event.1402 This is equivalent to a diff against an empty tree.1403 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1404 normally hide the root commit will now show it. True by default.14051406mailmap.file::1407 The location of an augmenting mailmap file. The default1408 mailmap, located in the root of the repository, is loaded1409 first, then the mailmap file pointed to by this variable.1410 The location of the mailmap file may be in a repository1411 subdirectory, or somewhere outside of the repository itself.1412 See linkgit:git-shortlog[1] and linkgit:git-blame[1].14131414man.viewer::1415 Specify the programs that may be used to display help in the1416 'man' format. See linkgit:git-help[1].14171418man.<tool>.cmd::1419 Specify the command to invoke the specified man viewer. The1420 specified command is evaluated in shell with the man page1421 passed as argument. (See linkgit:git-help[1].)14221423man.<tool>.path::1424 Override the path for the given tool that may be used to1425 display help in the 'man' format. See linkgit:git-help[1].14261427include::merge-config.txt[]14281429mergetool.<tool>.path::1430 Override the path for the given tool. This is useful in case1431 your tool is not in the PATH.14321433mergetool.<tool>.cmd::1434 Specify the command to invoke the specified merge tool. The1435 specified command is evaluated in shell with the following1436 variables available: 'BASE' is the name of a temporary file1437 containing the common base of the files to be merged, if available;1438 'LOCAL' is the name of a temporary file containing the contents of1439 the file on the current branch; 'REMOTE' is the name of a temporary1440 file containing the contents of the file from the branch being1441 merged; 'MERGED' contains the name of the file to which the merge1442 tool should write the results of a successful merge.14431444mergetool.<tool>.trustExitCode::1445 For a custom merge command, specify whether the exit code of1446 the merge command can be used to determine whether the merge was1447 successful. If this is not set to true then the merge target file1448 timestamp is checked and the merge assumed to have been successful1449 if the file has been updated, otherwise the user is prompted to1450 indicate the success of the merge.14511452mergetool.keepBackup::1453 After performing a merge, the original file with conflict markers1454 can be saved as a file with a `.orig` extension. If this variable1455 is set to `false` then this file is not preserved. Defaults to1456 `true` (i.e. keep the backup files).14571458mergetool.keepTemporaries::1459 When invoking a custom merge tool, git uses a set of temporary1460 files to pass to the tool. If the tool returns an error and this1461 variable is set to `true`, then these temporary files will be1462 preserved, otherwise they will be removed after the tool has1463 exited. Defaults to `false`.14641465mergetool.prompt::1466 Prompt before each invocation of the merge resolution program.14671468notes.displayRef::1469 The (fully qualified) refname from which to show notes when1470 showing commit messages. The value of this variable can be set1471 to a glob, in which case notes from all matching refs will be1472 shown. You may also specify this configuration variable1473 several times. A warning will be issued for refs that do not1474 exist, but a glob that does not match any refs is silently1475 ignored.1476+1477This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`1478environment variable, which must be a colon separated list of refs or1479globs.1480+1481The effective value of "core.notesRef" (possibly overridden by1482GIT_NOTES_REF) is also implicitly added to the list of refs to be1483displayed.14841485notes.rewrite.<command>::1486 When rewriting commits with <command> (currently `amend` or1487 `rebase`) and this variable is set to `true`, git1488 automatically copies your notes from the original to the1489 rewritten commit. Defaults to `true`, but see1490 "notes.rewriteRef" below.14911492notes.rewriteMode::1493 When copying notes during a rewrite (see the1494 "notes.rewrite.<command>" option), determines what to do if1495 the target commit already has a note. Must be one of1496 `overwrite`, `concatenate`, or `ignore`. Defaults to1497 `concatenate`.1498+1499This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`1500environment variable.15011502notes.rewriteRef::1503 When copying notes during a rewrite, specifies the (fully1504 qualified) ref whose notes should be copied. The ref may be a1505 glob, in which case notes in all matching refs will be copied.1506 You may also specify this configuration several times.1507+1508Does not have a default value; you must configure this variable to1509enable note rewriting. Set it to `refs/notes/commits` to enable1510rewriting for the default commit notes.1511+1512This setting can be overridden with the `GIT_NOTES_REWRITE_REF`1513environment variable, which must be a colon separated list of refs or1514globs.15151516pack.window::1517 The size of the window used by linkgit:git-pack-objects[1] when no1518 window size is given on the command line. Defaults to 10.15191520pack.depth::1521 The maximum delta depth used by linkgit:git-pack-objects[1] when no1522 maximum depth is given on the command line. Defaults to 50.15231524pack.windowMemory::1525 The window memory size limit used by linkgit:git-pack-objects[1]1526 when no limit is given on the command line. The value can be1527 suffixed with "k", "m", or "g". Defaults to 0, meaning no1528 limit.15291530pack.compression::1531 An integer -1..9, indicating the compression level for objects1532 in a pack file. -1 is the zlib default. 0 means no1533 compression, and 1..9 are various speed/size tradeoffs, 9 being1534 slowest. If not set, defaults to core.compression. If that is1535 not set, defaults to -1, the zlib default, which is "a default1536 compromise between speed and compression (currently equivalent1537 to level 6)."1538+1539Note that changing the compression level will not automatically recompress1540all existing objects. You can force recompression by passing the -F option1541to linkgit:git-repack[1].15421543pack.deltaCacheSize::1544 The maximum memory in bytes used for caching deltas in1545 linkgit:git-pack-objects[1] before writing them out to a pack.1546 This cache is used to speed up the writing object phase by not1547 having to recompute the final delta result once the best match1548 for all objects is found. Repacking large repositories on machines1549 which are tight with memory might be badly impacted by this though,1550 especially if this cache pushes the system into swapping.1551 A value of 0 means no limit. The smallest size of 1 byte may be1552 used to virtually disable this cache. Defaults to 256 MiB.15531554pack.deltaCacheLimit::1555 The maximum size of a delta, that is cached in1556 linkgit:git-pack-objects[1]. This cache is used to speed up the1557 writing object phase by not having to recompute the final delta1558 result once the best match for all objects is found. Defaults to 1000.15591560pack.threads::1561 Specifies the number of threads to spawn when searching for best1562 delta matches. This requires that linkgit:git-pack-objects[1]1563 be compiled with pthreads otherwise this option is ignored with a1564 warning. This is meant to reduce packing time on multiprocessor1565 machines. The required amount of memory for the delta search window1566 is however multiplied by the number of threads.1567 Specifying 0 will cause git to auto-detect the number of CPU's1568 and set the number of threads accordingly.15691570pack.indexVersion::1571 Specify the default pack index version. Valid values are 1 for1572 legacy pack index used by Git versions prior to 1.5.2, and 2 for1573 the new pack index with capabilities for packs larger than 4 GB1574 as well as proper protection against the repacking of corrupted1575 packs. Version 2 is the default. Note that version 2 is enforced1576 and this config option ignored whenever the corresponding pack is1577 larger than 2 GB.1578+1579If you have an old git that does not understand the version 2 `{asterisk}.idx` file,1580cloning or fetching over a non native protocol (e.g. "http" and "rsync")1581that will copy both `{asterisk}.pack` file and corresponding `{asterisk}.idx` file from the1582other side may give you a repository that cannot be accessed with your1583older version of git. If the `{asterisk}.pack` file is smaller than 2 GB, however,1584you can use linkgit:git-index-pack[1] on the *.pack file to regenerate1585the `{asterisk}.idx` file.15861587pack.packSizeLimit::1588 The maximum size of a pack. This setting only affects1589 packing to a file when repacking, i.e. the git:// protocol1590 is unaffected. It can be overridden by the `\--max-pack-size`1591 option of linkgit:git-repack[1]. The minimum size allowed is1592 limited to 1 MiB. The default is unlimited.1593 Common unit suffixes of 'k', 'm', or 'g' are1594 supported.15951596pager.<cmd>::1597 If the value is boolean, turns on or off pagination of the1598 output of a particular git subcommand when writing to a tty.1599 Otherwise, turns on pagination for the subcommand using the1600 pager specified by the value of `pager.<cmd>`. If `\--paginate`1601 or `\--no-pager` is specified on the command line, it takes1602 precedence over this option. To disable pagination for all1603 commands, set `core.pager` or `GIT_PAGER` to `cat`.16041605pretty.<name>::1606 Alias for a --pretty= format string, as specified in1607 linkgit:git-log[1]. Any aliases defined here can be used just1608 as the built-in pretty formats could. For example,1609 running `git config pretty.changelog "format:{asterisk} %H %s"`1610 would cause the invocation `git log --pretty=changelog`1611 to be equivalent to running `git log "--pretty=format:{asterisk} %H %s"`.1612 Note that an alias with the same name as a built-in format1613 will be silently ignored.16141615pull.rebase::1616 When true, rebase branches on top of the fetched branch, instead1617 of merging the default branch from the default remote when "git1618 pull" is run. See "branch.<name>.rebase" for setting this on a1619 per-branch basis.1620+1621*NOTE*: this is a possibly dangerous operation; do *not* use1622it unless you understand the implications (see linkgit:git-rebase[1]1623for details).16241625pull.octopus::1626 The default merge strategy to use when pulling multiple branches1627 at once.16281629pull.twohead::1630 The default merge strategy to use when pulling a single branch.16311632push.default::1633 Defines the action git push should take if no refspec is given1634 on the command line, no refspec is configured in the remote, and1635 no refspec is implied by any of the options given on the command1636 line. Possible values are:1637+1638* `nothing` - do not push anything.1639* `matching` - push all matching branches.1640 All branches having the same name in both ends are considered to be1641 matching. This is the default.1642* `upstream` - push the current branch to its upstream branch.1643* `tracking` - deprecated synonym for `upstream`.1644* `current` - push the current branch to a branch of the same name.16451646rebase.stat::1647 Whether to show a diffstat of what changed upstream since the last1648 rebase. False by default.16491650rebase.autosquash::1651 If set to true enable '--autosquash' option by default.16521653receive.autogc::1654 By default, git-receive-pack will run "git-gc --auto" after1655 receiving data from git-push and updating refs. You can stop1656 it by setting this variable to false.16571658receive.fsckObjects::1659 If it is set to true, git-receive-pack will check all received1660 objects. It will abort in the case of a malformed object or a1661 broken link. The result of an abort are only dangling objects.1662 Defaults to false. If not set, the value of `transfer.fsckObjects`1663 is used instead.16641665receive.unpackLimit::1666 If the number of objects received in a push is below this1667 limit then the objects will be unpacked into loose object1668 files. However if the number of received objects equals or1669 exceeds this limit then the received pack will be stored as1670 a pack, after adding any missing delta bases. Storing the1671 pack from a push can make the push operation complete faster,1672 especially on slow filesystems. If not set, the value of1673 `transfer.unpackLimit` is used instead.16741675receive.denyDeletes::1676 If set to true, git-receive-pack will deny a ref update that deletes1677 the ref. Use this to prevent such a ref deletion via a push.16781679receive.denyDeleteCurrent::1680 If set to true, git-receive-pack will deny a ref update that1681 deletes the currently checked out branch of a non-bare repository.16821683receive.denyCurrentBranch::1684 If set to true or "refuse", git-receive-pack will deny a ref update1685 to the currently checked out branch of a non-bare repository.1686 Such a push is potentially dangerous because it brings the HEAD1687 out of sync with the index and working tree. If set to "warn",1688 print a warning of such a push to stderr, but allow the push to1689 proceed. If set to false or "ignore", allow such pushes with no1690 message. Defaults to "refuse".16911692receive.denyNonFastForwards::1693 If set to true, git-receive-pack will deny a ref update which is1694 not a fast-forward. Use this to prevent such an update via a push,1695 even if that push is forced. This configuration variable is1696 set when initializing a shared repository.16971698receive.updateserverinfo::1699 If set to true, git-receive-pack will run git-update-server-info1700 after receiving data from git-push and updating refs.17011702remote.<name>.url::1703 The URL of a remote repository. See linkgit:git-fetch[1] or1704 linkgit:git-push[1].17051706remote.<name>.pushurl::1707 The push URL of a remote repository. See linkgit:git-push[1].17081709remote.<name>.proxy::1710 For remotes that require curl (http, https and ftp), the URL to1711 the proxy to use for that remote. Set to the empty string to1712 disable proxying for that remote.17131714remote.<name>.fetch::1715 The default set of "refspec" for linkgit:git-fetch[1]. See1716 linkgit:git-fetch[1].17171718remote.<name>.push::1719 The default set of "refspec" for linkgit:git-push[1]. See1720 linkgit:git-push[1].17211722remote.<name>.mirror::1723 If true, pushing to this remote will automatically behave1724 as if the `\--mirror` option was given on the command line.17251726remote.<name>.skipDefaultUpdate::1727 If true, this remote will be skipped by default when updating1728 using linkgit:git-fetch[1] or the `update` subcommand of1729 linkgit:git-remote[1].17301731remote.<name>.skipFetchAll::1732 If true, this remote will be skipped by default when updating1733 using linkgit:git-fetch[1] or the `update` subcommand of1734 linkgit:git-remote[1].17351736remote.<name>.receivepack::1737 The default program to execute on the remote side when pushing. See1738 option \--receive-pack of linkgit:git-push[1].17391740remote.<name>.uploadpack::1741 The default program to execute on the remote side when fetching. See1742 option \--upload-pack of linkgit:git-fetch-pack[1].17431744remote.<name>.tagopt::1745 Setting this value to \--no-tags disables automatic tag following when1746 fetching from remote <name>. Setting it to \--tags will fetch every1747 tag from remote <name>, even if they are not reachable from remote1748 branch heads. Passing these flags directly to linkgit:git-fetch[1] can1749 override this setting. See options \--tags and \--no-tags of1750 linkgit:git-fetch[1].17511752remote.<name>.vcs::1753 Setting this to a value <vcs> will cause git to interact with1754 the remote with the git-remote-<vcs> helper.17551756remotes.<group>::1757 The list of remotes which are fetched by "git remote update1758 <group>". See linkgit:git-remote[1].17591760repack.usedeltabaseoffset::1761 By default, linkgit:git-repack[1] creates packs that use1762 delta-base offset. If you need to share your repository with1763 git older than version 1.4.4, either directly or via a dumb1764 protocol such as http, then you need to set this option to1765 "false" and repack. Access from old git versions over the1766 native protocol are unaffected by this option.17671768rerere.autoupdate::1769 When set to true, `git-rerere` updates the index with the1770 resulting contents after it cleanly resolves conflicts using1771 previously recorded resolution. Defaults to false.17721773rerere.enabled::1774 Activate recording of resolved conflicts, so that identical1775 conflict hunks can be resolved automatically, should they be1776 encountered again. By default, linkgit:git-rerere[1] is1777 enabled if there is an `rr-cache` directory under the1778 `$GIT_DIR`.17791780sendemail.identity::1781 A configuration identity. When given, causes values in the1782 'sendemail.<identity>' subsection to take precedence over1783 values in the 'sendemail' section. The default identity is1784 the value of 'sendemail.identity'.17851786sendemail.smtpencryption::1787 See linkgit:git-send-email[1] for description. Note that this1788 setting is not subject to the 'identity' mechanism.17891790sendemail.smtpssl::1791 Deprecated alias for 'sendemail.smtpencryption = ssl'.17921793sendemail.<identity>.*::1794 Identity-specific versions of the 'sendemail.*' parameters1795 found below, taking precedence over those when the this1796 identity is selected, through command-line or1797 'sendemail.identity'.17981799sendemail.aliasesfile::1800sendemail.aliasfiletype::1801sendemail.bcc::1802sendemail.cc::1803sendemail.cccmd::1804sendemail.chainreplyto::1805sendemail.confirm::1806sendemail.envelopesender::1807sendemail.from::1808sendemail.multiedit::1809sendemail.signedoffbycc::1810sendemail.smtppass::1811sendemail.suppresscc::1812sendemail.suppressfrom::1813sendemail.to::1814sendemail.smtpdomain::1815sendemail.smtpserver::1816sendemail.smtpserverport::1817sendemail.smtpserveroption::1818sendemail.smtpuser::1819sendemail.thread::1820sendemail.validate::1821 See linkgit:git-send-email[1] for description.18221823sendemail.signedoffcc::1824 Deprecated alias for 'sendemail.signedoffbycc'.18251826showbranch.default::1827 The default set of branches for linkgit:git-show-branch[1].1828 See linkgit:git-show-branch[1].18291830status.relativePaths::1831 By default, linkgit:git-status[1] shows paths relative to the1832 current directory. Setting this variable to `false` shows paths1833 relative to the repository root (this was the default for git1834 prior to v1.5.4).18351836status.showUntrackedFiles::1837 By default, linkgit:git-status[1] and linkgit:git-commit[1] show1838 files which are not currently tracked by Git. Directories which1839 contain only untracked files, are shown with the directory name1840 only. Showing untracked files means that Git needs to lstat() all1841 all the files in the whole repository, which might be slow on some1842 systems. So, this variable controls how the commands displays1843 the untracked files. Possible values are:1844+1845--1846* `no` - Show no untracked files.1847* `normal` - Show untracked files and directories.1848* `all` - Show also individual files in untracked directories.1849--1850+1851If this variable is not specified, it defaults to 'normal'.1852This variable can be overridden with the -u|--untracked-files option1853of linkgit:git-status[1] and linkgit:git-commit[1].18541855status.submodulesummary::1856 Defaults to false.1857 If this is set to a non zero number or true (identical to -1 or an1858 unlimited number), the submodule summary will be enabled and a1859 summary of commits for modified submodules will be shown (see1860 --summary-limit option of linkgit:git-submodule[1]).18611862submodule.<name>.path::1863submodule.<name>.url::1864submodule.<name>.update::1865 The path within this project, URL, and the updating strategy1866 for a submodule. These variables are initially populated1867 by 'git submodule init'; edit them to override the1868 URL and other values found in the `.gitmodules` file. See1869 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.18701871submodule.<name>.fetchRecurseSubmodules::1872 This option can be used to control recursive fetching of this1873 submodule. It can be overridden by using the --[no-]recurse-submodules1874 command line option to "git fetch" and "git pull".1875 This setting will override that from in the linkgit:gitmodules[5]1876 file.18771878submodule.<name>.ignore::1879 Defines under what circumstances "git status" and the diff family show1880 a submodule as modified. When set to "all", it will never be considered1881 modified, "dirty" will ignore all changes to the submodules work tree and1882 takes only differences between the HEAD of the submodule and the commit1883 recorded in the superproject into account. "untracked" will additionally1884 let submodules with modified tracked files in their work tree show up.1885 Using "none" (the default when this option is not set) also shows1886 submodules that have untracked files in their work tree as changed.1887 This setting overrides any setting made in .gitmodules for this submodule,1888 both settings can be overridden on the command line by using the1889 "--ignore-submodules" option.18901891tar.umask::1892 This variable can be used to restrict the permission bits of1893 tar archive entries. The default is 0002, which turns off the1894 world write bit. The special value "user" indicates that the1895 archiving user's umask will be used instead. See umask(2) and1896 linkgit:git-archive[1].18971898transfer.fsckObjects::1899 When `fetch.fsckObjects` or `receive.fsckObjects` are1900 not set, the value of this variable is used instead.1901 Defaults to false.19021903transfer.unpackLimit::1904 When `fetch.unpackLimit` or `receive.unpackLimit` are1905 not set, the value of this variable is used instead.1906 The default value is 100.19071908url.<base>.insteadOf::1909 Any URL that starts with this value will be rewritten to1910 start, instead, with <base>. In cases where some site serves a1911 large number of repositories, and serves them with multiple1912 access methods, and some users need to use different access1913 methods, this feature allows people to specify any of the1914 equivalent URLs and have git automatically rewrite the URL to1915 the best alternative for the particular user, even for a1916 never-before-seen repository on the site. When more than one1917 insteadOf strings match a given URL, the longest match is used.19181919url.<base>.pushInsteadOf::1920 Any URL that starts with this value will not be pushed to;1921 instead, it will be rewritten to start with <base>, and the1922 resulting URL will be pushed to. In cases where some site serves1923 a large number of repositories, and serves them with multiple1924 access methods, some of which do not allow push, this feature1925 allows people to specify a pull-only URL and have git1926 automatically use an appropriate URL to push, even for a1927 never-before-seen repository on the site. When more than one1928 pushInsteadOf strings match a given URL, the longest match is1929 used. If a remote has an explicit pushurl, git will ignore this1930 setting for that remote.19311932user.email::1933 Your email address to be recorded in any newly created commits.1934 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and1935 'EMAIL' environment variables. See linkgit:git-commit-tree[1].19361937user.name::1938 Your full name to be recorded in any newly created commits.1939 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'1940 environment variables. See linkgit:git-commit-tree[1].19411942user.signingkey::1943 If linkgit:git-tag[1] is not selecting the key you want it to1944 automatically when creating a signed tag, you can override the1945 default selection with this variable. This option is passed1946 unchanged to gpg's --local-user parameter, so you may specify a key1947 using any method that gpg supports.19481949web.browser::1950 Specify a web browser that may be used by some commands.1951 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]1952 may use it.