1CONFIGURATION FILE 2------------------ 3 4The Git configuration file contains a number of variables that affect 5the Git commands' 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). Other char escape sequences (including octal 82escape sequences) are invalid. 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: `~/` 99is expanded to the value of `$HOME`, and `~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. 135 136Other git-related tools may and do use their own variables. When 137inventing new variables for use in your own tool, make sure their 138names do not conflict with those that are used by Git itself and 139other popular tools, and describe them in your documentation. 140 141 142advice.*:: 143 These variables control various optional help messages designed to 144 aid new users. All 'advice.*' variables default to 'true', and you 145 can tell Git that you do not need help by setting these to 'false': 146+ 147-- 148 pushUpdateRejected:: 149 Set this variable to 'false' if you want to disable 150 'pushNonFFCurrent', 151 'pushNonFFMatching', 'pushAlreadyExists', 152 'pushFetchFirst', and 'pushNeedsForce' 153 simultaneously. 154 pushNonFFCurrent:: 155 Advice shown when linkgit:git-push[1] fails due to a 156 non-fast-forward update to the current branch. 157 pushNonFFMatching:: 158 Advice shown when you ran linkgit:git-push[1] and pushed 159 'matching refs' explicitly (i.e. you used ':', or 160 specified a refspec that isn't your current branch) and 161 it resulted in a non-fast-forward error. 162 pushAlreadyExists:: 163 Shown when linkgit:git-push[1] rejects an update that 164 does not qualify for fast-forwarding (e.g., a tag.) 165 pushFetchFirst:: 166 Shown when linkgit:git-push[1] rejects an update that 167 tries to overwrite a remote ref that points at an 168 object we do not have. 169 pushNeedsForce:: 170 Shown when linkgit:git-push[1] rejects an update that 171 tries to overwrite a remote ref that points at an 172 object that is not a commit-ish, or make the remote 173 ref point at an object that is not a commit-ish. 174 statusHints:: 175 Show directions on how to proceed from the current 176 state in the output of linkgit:git-status[1], in 177 the template shown when writing commit messages in 178 linkgit:git-commit[1], and in the help message shown 179 by linkgit:git-checkout[1] when switching branch. 180 statusUoption:: 181 Advise to consider using the `-u` option to linkgit:git-status[1] 182 when the command takes more than 2 seconds to enumerate untracked 183 files. 184 commitBeforeMerge:: 185 Advice shown when linkgit:git-merge[1] refuses to 186 merge to avoid overwriting local changes. 187 resolveConflict:: 188 Advice shown by various commands when conflicts 189 prevent the operation from being performed. 190 implicitIdentity:: 191 Advice on how to set your identity configuration when 192 your information is guessed from the system username and 193 domain name. 194 detachedHead:: 195 Advice shown when you used linkgit:git-checkout[1] to 196 move to the detach HEAD state, to instruct how to create 197 a local branch after the fact. 198 amWorkDir:: 199 Advice that shows the location of the patch file when 200 linkgit:git-am[1] fails to apply it. 201 rmHints:: 202 In case of failure in the output of linkgit:git-rm[1], 203 show directions on how to proceed from the current state. 204-- 205 206core.fileMode:: 207 Tells Git if the executable bit of files in the working tree 208 is to be honored. 209+ 210Some filesystems lose the executable bit when a file that is 211marked as executable is checked out, or checks out an 212non-executable file with executable bit on. 213linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem 214to see if it handles the executable bit correctly 215and this variable is automatically set as necessary. 216+ 217A repository, however, may be on a filesystem that handles 218the filemode correctly, and this variable is set to 'true' 219when created, but later may be made accessible from another 220environment that loses the filemode (e.g. exporting ext4 via 221CIFS mount, visiting a Cygwin created repository with 222Git for Windows or Eclipse). 223In such a case it may be necessary to set this variable to 'false'. 224See linkgit:git-update-index[1]. 225+ 226The default is true (when core.filemode is not specified in the config file). 227 228core.ignorecase:: 229 If true, this option enables various workarounds to enable 230 Git to work better on filesystems that are not case sensitive, 231 like FAT. For example, if a directory listing finds 232 "makefile" when Git expects "Makefile", Git will assume 233 it is really the same file, and continue to remember it as 234 "Makefile". 235+ 236The default is false, except linkgit:git-clone[1] or linkgit:git-init[1] 237will probe and set core.ignorecase true if appropriate when the repository 238is created. 239 240core.precomposeunicode:: 241 This option is only used by Mac OS implementation of Git. 242 When core.precomposeunicode=true, Git reverts the unicode decomposition 243 of filenames done by Mac OS. This is useful when sharing a repository 244 between Mac OS and Linux or Windows. 245 (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). 246 When false, file names are handled fully transparent by Git, 247 which is backward compatible with older versions of Git. 248 249core.trustctime:: 250 If false, the ctime differences between the index and the 251 working tree are ignored; useful when the inode change time 252 is regularly modified by something outside Git (file system 253 crawlers and some backup systems). 254 See linkgit:git-update-index[1]. True by default. 255 256core.checkstat:: 257 Determines which stat fields to match between the index 258 and work tree. The user can set this to 'default' or 259 'minimal'. Default (or explicitly 'default'), is to check 260 all fields, including the sub-second part of mtime and ctime. 261 262core.quotepath:: 263 The commands that output paths (e.g. 'ls-files', 264 'diff'), when not given the `-z` option, will quote 265 "unusual" characters in the pathname by enclosing the 266 pathname in a double-quote pair and with backslashes the 267 same way strings in C source code are quoted. If this 268 variable is set to false, the bytes higher than 0x80 are 269 not quoted but output as verbatim. Note that double 270 quote, backslash and control characters are always 271 quoted without `-z` regardless of the setting of this 272 variable. 273 274core.eol:: 275 Sets the line ending type to use in the working directory for 276 files that have the `text` property set. Alternatives are 277 'lf', 'crlf' and 'native', which uses the platform's native 278 line ending. The default value is `native`. See 279 linkgit:gitattributes[5] for more information on end-of-line 280 conversion. 281 282core.safecrlf:: 283 If true, makes Git check if converting `CRLF` is reversible when 284 end-of-line conversion is active. Git will verify if a command 285 modifies a file in the work tree either directly or indirectly. 286 For example, committing a file followed by checking out the 287 same file should yield the original file in the work tree. If 288 this is not the case for the current setting of 289 `core.autocrlf`, Git will reject the file. The variable can 290 be set to "warn", in which case Git will only warn about an 291 irreversible conversion but continue the operation. 292+ 293CRLF conversion bears a slight chance of corrupting data. 294When it is enabled, Git will convert CRLF to LF during commit and LF to 295CRLF during checkout. A file that contains a mixture of LF and 296CRLF before the commit cannot be recreated by Git. For text 297files this is the right thing to do: it corrects line endings 298such that we have only LF line endings in the repository. 299But for binary files that are accidentally classified as text the 300conversion can corrupt data. 301+ 302If you recognize such corruption early you can easily fix it by 303setting the conversion type explicitly in .gitattributes. Right 304after committing you still have the original file in your work 305tree and this file is not yet corrupted. You can explicitly tell 306Git that this file is binary and Git will handle the file 307appropriately. 308+ 309Unfortunately, the desired effect of cleaning up text files with 310mixed line endings and the undesired effect of corrupting binary 311files cannot be distinguished. In both cases CRLFs are removed 312in an irreversible way. For text files this is the right thing 313to do because CRLFs are line endings, while for binary files 314converting CRLFs corrupts data. 315+ 316Note, this safety check does not mean that a checkout will generate a 317file identical to the original file for a different setting of 318`core.eol` and `core.autocrlf`, but only for the current one. For 319example, a text file with `LF` would be accepted with `core.eol=lf` 320and could later be checked out with `core.eol=crlf`, in which case the 321resulting file would contain `CRLF`, although the original file 322contained `LF`. However, in both work trees the line endings would be 323consistent, that is either all `LF` or all `CRLF`, but never mixed. A 324file with mixed line endings would be reported by the `core.safecrlf` 325mechanism. 326 327core.autocrlf:: 328 Setting this variable to "true" is almost the same as setting 329 the `text` attribute to "auto" on all files except that text 330 files are not guaranteed to be normalized: files that contain 331 `CRLF` in the repository will not be touched. Use this 332 setting if you want to have `CRLF` line endings in your 333 working directory even though the repository does not have 334 normalized line endings. This variable can be set to 'input', 335 in which case no output conversion is performed. 336 337core.symlinks:: 338 If false, symbolic links are checked out as small plain files that 339 contain the link text. linkgit:git-update-index[1] and 340 linkgit:git-add[1] will not change the recorded type to regular 341 file. Useful on filesystems like FAT that do not support 342 symbolic links. 343+ 344The default is true, except linkgit:git-clone[1] or linkgit:git-init[1] 345will probe and set core.symlinks false if appropriate when the repository 346is created. 347 348core.gitProxy:: 349 A "proxy command" to execute (as 'command host port') instead 350 of establishing direct connection to the remote server when 351 using the Git protocol for fetching. If the variable value is 352 in the "COMMAND for DOMAIN" format, the command is applied only 353 on hostnames ending with the specified domain string. This variable 354 may be set multiple times and is matched in the given order; 355 the first match wins. 356+ 357Can be overridden by the 'GIT_PROXY_COMMAND' environment variable 358(which always applies universally, without the special "for" 359handling). 360+ 361The special string `none` can be used as the proxy command to 362specify that no proxy be used for a given domain pattern. 363This is useful for excluding servers inside a firewall from 364proxy use, while defaulting to a common proxy for external domains. 365 366core.ignoreStat:: 367 If true, commands which modify both the working tree and the index 368 will mark the updated paths with the "assume unchanged" bit in the 369 index. These marked files are then assumed to stay unchanged in the 370 working tree, until you mark them otherwise manually - Git will not 371 detect the file changes by lstat() calls. This is useful on systems 372 where those are very slow, such as Microsoft Windows. 373 See linkgit:git-update-index[1]. 374 False by default. 375 376core.preferSymlinkRefs:: 377 Instead of the default "symref" format for HEAD 378 and other symbolic reference files, use symbolic links. 379 This is sometimes needed to work with old scripts that 380 expect HEAD to be a symbolic link. 381 382core.bare:: 383 If true this repository is assumed to be 'bare' and has no 384 working directory associated with it. If this is the case a 385 number of commands that require a working directory will be 386 disabled, such as linkgit:git-add[1] or linkgit:git-merge[1]. 387+ 388This setting is automatically guessed by linkgit:git-clone[1] or 389linkgit:git-init[1] when the repository was created. By default a 390repository that ends in "/.git" is assumed to be not bare (bare = 391false), while all other repositories are assumed to be bare (bare 392= true). 393 394core.worktree:: 395 Set the path to the root of the working tree. 396 This can be overridden by the GIT_WORK_TREE environment 397 variable and the '--work-tree' command-line option. 398 The value can be an absolute path or relative to the path to 399 the .git directory, which is either specified by --git-dir 400 or GIT_DIR, or automatically discovered. 401 If --git-dir or GIT_DIR is specified but none of 402 --work-tree, GIT_WORK_TREE and core.worktree is specified, 403 the current working directory is regarded as the top level 404 of your working tree. 405+ 406Note that this variable is honored even when set in a configuration 407file in a ".git" subdirectory of a directory and its value differs 408from the latter directory (e.g. "/path/to/.git/config" has 409core.worktree set to "/different/path"), which is most likely a 410misconfiguration. Running Git commands in the "/path/to" directory will 411still use "/different/path" as the root of the work tree and can cause 412confusion unless you know what you are doing (e.g. you are creating a 413read-only snapshot of the same index to a location different from the 414repository's usual working tree). 415 416core.logAllRefUpdates:: 417 Enable the reflog. Updates to a ref <ref> is logged to the file 418 "$GIT_DIR/logs/<ref>", by appending the new and old 419 SHA-1, the date/time and the reason of the update, but 420 only when the file exists. If this configuration 421 variable is set to true, missing "$GIT_DIR/logs/<ref>" 422 file is automatically created for branch heads (i.e. under 423 refs/heads/), remote refs (i.e. under refs/remotes/), 424 note refs (i.e. under refs/notes/), and the symbolic ref HEAD. 425+ 426This information can be used to determine what commit 427was the tip of a branch "2 days ago". 428+ 429This value is true by default in a repository that has 430a working directory associated with it, and false by 431default in a bare repository. 432 433core.repositoryFormatVersion:: 434 Internal variable identifying the repository format and layout 435 version. 436 437core.sharedRepository:: 438 When 'group' (or 'true'), the repository is made shareable between 439 several users in a group (making sure all the files and objects are 440 group-writable). When 'all' (or 'world' or 'everybody'), the 441 repository will be readable by all users, additionally to being 442 group-shareable. When 'umask' (or 'false'), Git will use permissions 443 reported by umask(2). When '0xxx', where '0xxx' is an octal number, 444 files in the repository will have this mode value. '0xxx' will override 445 user's umask value (whereas the other options will only override 446 requested parts of the user's umask value). Examples: '0660' will make 447 the repo read/write-able for the owner and group, but inaccessible to 448 others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a 449 repository that is group-readable but not group-writable. 450 See linkgit:git-init[1]. False by default. 451 452core.warnAmbiguousRefs:: 453 If true, Git will warn you if the ref name you passed it is ambiguous 454 and might match multiple refs in the repository. True by default. 455 456core.compression:: 457 An integer -1..9, indicating a default compression level. 458 -1 is the zlib default. 0 means no compression, 459 and 1..9 are various speed/size tradeoffs, 9 being slowest. 460 If set, this provides a default to other compression variables, 461 such as 'core.loosecompression' and 'pack.compression'. 462 463core.loosecompression:: 464 An integer -1..9, indicating the compression level for objects that 465 are not in a pack file. -1 is the zlib default. 0 means no 466 compression, and 1..9 are various speed/size tradeoffs, 9 being 467 slowest. If not set, defaults to core.compression. If that is 468 not set, defaults to 1 (best speed). 469 470core.packedGitWindowSize:: 471 Number of bytes of a pack file to map into memory in a 472 single mapping operation. Larger window sizes may allow 473 your system to process a smaller number of large pack files 474 more quickly. Smaller window sizes will negatively affect 475 performance due to increased calls to the operating system's 476 memory manager, but may improve performance when accessing 477 a large number of large pack files. 478+ 479Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32 480MiB on 32 bit platforms and 1 GiB on 64 bit platforms. This should 481be reasonable for all users/operating systems. You probably do 482not need to adjust this value. 483+ 484Common unit suffixes of 'k', 'm', or 'g' are supported. 485 486core.packedGitLimit:: 487 Maximum number of bytes to map simultaneously into memory 488 from pack files. If Git needs to access more than this many 489 bytes at once to complete an operation it will unmap existing 490 regions to reclaim virtual address space within the process. 491+ 492Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms. 493This should be reasonable for all users/operating systems, except on 494the largest projects. You probably do not need to adjust this value. 495+ 496Common unit suffixes of 'k', 'm', or 'g' are supported. 497 498core.deltaBaseCacheLimit:: 499 Maximum number of bytes to reserve for caching base objects 500 that may be referenced by multiple deltified objects. By storing the 501 entire decompressed base objects in a cache Git is able 502 to avoid unpacking and decompressing frequently used base 503 objects multiple times. 504+ 505Default is 96 MiB on all platforms. This should be reasonable 506for all users/operating systems, except on the largest projects. 507You probably do not need to adjust this value. 508+ 509Common unit suffixes of 'k', 'm', or 'g' are supported. 510 511core.bigFileThreshold:: 512 Files larger than this size are stored deflated, without 513 attempting delta compression. Storing large files without 514 delta compression avoids excessive memory usage, at the 515 slight expense of increased disk usage. Additionally files 516 larger than this size are always treated as binary. 517+ 518Default is 512 MiB on all platforms. This should be reasonable 519for most projects as source code and other text files can still 520be delta compressed, but larger binary media files won't be. 521+ 522Common unit suffixes of 'k', 'm', or 'g' are supported. 523 524core.excludesfile:: 525 In addition to '.gitignore' (per-directory) and 526 '.git/info/exclude', Git looks into this file for patterns 527 of files which are not meant to be tracked. "`~/`" is expanded 528 to the value of `$HOME` and "`~user/`" to the specified user's 529 home directory. Its default value is $XDG_CONFIG_HOME/git/ignore. 530 If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore 531 is used instead. See linkgit:gitignore[5]. 532 533core.askpass:: 534 Some commands (e.g. svn and http interfaces) that interactively 535 ask for a password can be told to use an external program given 536 via the value of this variable. Can be overridden by the 'GIT_ASKPASS' 537 environment variable. If not set, fall back to the value of the 538 'SSH_ASKPASS' environment variable or, failing that, a simple password 539 prompt. The external program shall be given a suitable prompt as 540 command-line argument and write the password on its STDOUT. 541 542core.attributesfile:: 543 In addition to '.gitattributes' (per-directory) and 544 '.git/info/attributes', Git looks into this file for attributes 545 (see linkgit:gitattributes[5]). Path expansions are made the same 546 way as for `core.excludesfile`. Its default value is 547 $XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not 548 set or empty, $HOME/.config/git/attributes is used instead. 549 550core.editor:: 551 Commands such as `commit` and `tag` that lets you edit 552 messages by launching an editor uses the value of this 553 variable when it is set, and the environment variable 554 `GIT_EDITOR` is not set. See linkgit:git-var[1]. 555 556core.commentchar:: 557 Commands such as `commit` and `tag` that lets you edit 558 messages consider a line that begins with this character 559 commented, and removes them after the editor returns 560 (default '#'). 561+ 562If set to "auto", `git-commit` would select a character that is not 563the beginning character of any line in existing commit messages. 564 565sequence.editor:: 566 Text editor used by `git rebase -i` for editing the rebase instruction file. 567 The value is meant to be interpreted by the shell when it is used. 568 It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable. 569 When not configured the default commit message editor is used instead. 570 571core.pager:: 572 Text viewer for use by Git commands (e.g., 'less'). The value 573 is meant to be interpreted by the shell. The order of preference 574 is the `$GIT_PAGER` environment variable, then `core.pager` 575 configuration, then `$PAGER`, and then the default chosen at 576 compile time (usually 'less'). 577+ 578When the `LESS` environment variable is unset, Git sets it to `FRX` 579(if `LESS` environment variable is set, Git does not change it at 580all). If you want to selectively override Git's default setting 581for `LESS`, you can set `core.pager` to e.g. `less -S`. This will 582be passed to the shell by Git, which will translate the final 583command to `LESS=FRX less -S`. The environment does not set the 584`S` option but the command line does, instructing less to truncate 585long lines. Similarly, setting `core.pager` to `less -+F` will 586deactivate the `F` option specified by the environment from the 587command-line, deactivating the "quit if one screen" behavior of 588`less`. One can specifically activate some flags for particular 589commands: for example, setting `pager.blame` to `less -S` enables 590line truncation only for `git blame`. 591+ 592Likewise, when the `LV` environment variable is unset, Git sets it 593to `-c`. You can override this setting by exporting `LV` with 594another value or setting `core.pager` to `lv +c`. 595 596core.whitespace:: 597 A comma separated list of common whitespace problems to 598 notice. 'git diff' will use `color.diff.whitespace` to 599 highlight them, and 'git apply --whitespace=error' will 600 consider them as errors. You can prefix `-` to disable 601 any of them (e.g. `-trailing-space`): 602+ 603* `blank-at-eol` treats trailing whitespaces at the end of the line 604 as an error (enabled by default). 605* `space-before-tab` treats a space character that appears immediately 606 before a tab character in the initial indent part of the line as an 607 error (enabled by default). 608* `indent-with-non-tab` treats a line that is indented with space 609 characters instead of the equivalent tabs as an error (not enabled by 610 default). 611* `tab-in-indent` treats a tab character in the initial indent part of 612 the line as an error (not enabled by default). 613* `blank-at-eof` treats blank lines added at the end of file as an error 614 (enabled by default). 615* `trailing-space` is a short-hand to cover both `blank-at-eol` and 616 `blank-at-eof`. 617* `cr-at-eol` treats a carriage-return at the end of line as 618 part of the line terminator, i.e. with it, `trailing-space` 619 does not trigger if the character before such a carriage-return 620 is not a whitespace (not enabled by default). 621* `tabwidth=<n>` tells how many character positions a tab occupies; this 622 is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent` 623 errors. The default tab width is 8. Allowed values are 1 to 63. 624 625core.fsyncobjectfiles:: 626 This boolean will enable 'fsync()' when writing object files. 627+ 628This is a total waste of time and effort on a filesystem that orders 629data writes properly, but can be useful for filesystems that do not use 630journalling (traditional UNIX filesystems) or that only journal metadata 631and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback"). 632 633core.preloadindex:: 634 Enable parallel index preload for operations like 'git diff' 635+ 636This can speed up operations like 'git diff' and 'git status' especially 637on filesystems like NFS that have weak caching semantics and thus 638relatively high IO latencies. When enabled, Git will do the 639index comparison to the filesystem data in parallel, allowing 640overlapping IO's. Defaults to true. 641 642core.createObject:: 643 You can set this to 'link', in which case a hardlink followed by 644 a delete of the source are used to make sure that object creation 645 will not overwrite existing objects. 646+ 647On some file system/operating system combinations, this is unreliable. 648Set this config setting to 'rename' there; However, This will remove the 649check that makes sure that existing object files will not get overwritten. 650 651core.notesRef:: 652 When showing commit messages, also show notes which are stored in 653 the given ref. The ref must be fully qualified. If the given 654 ref does not exist, it is not an error but means that no 655 notes should be printed. 656+ 657This setting defaults to "refs/notes/commits", and it can be overridden by 658the 'GIT_NOTES_REF' environment variable. See linkgit:git-notes[1]. 659 660core.sparseCheckout:: 661 Enable "sparse checkout" feature. See section "Sparse checkout" in 662 linkgit:git-read-tree[1] for more information. 663 664core.abbrev:: 665 Set the length object names are abbreviated to. If unspecified, 666 many commands abbreviate to 7 hexdigits, which may not be enough 667 for abbreviated object names to stay unique for sufficiently long 668 time. 669 670add.ignore-errors:: 671add.ignoreErrors:: 672 Tells 'git add' to continue adding files when some files cannot be 673 added due to indexing errors. Equivalent to the '--ignore-errors' 674 option of linkgit:git-add[1]. Older versions of Git accept only 675 `add.ignore-errors`, which does not follow the usual naming 676 convention for configuration variables. Newer versions of Git 677 honor `add.ignoreErrors` as well. 678 679alias.*:: 680 Command aliases for the linkgit:git[1] command wrapper - e.g. 681 after defining "alias.last = cat-file commit HEAD", the invocation 682 "git last" is equivalent to "git cat-file commit HEAD". To avoid 683 confusion and troubles with script usage, aliases that 684 hide existing Git commands are ignored. Arguments are split by 685 spaces, the usual shell quoting and escaping is supported. 686 quote pair and a backslash can be used to quote them. 687+ 688If the alias expansion is prefixed with an exclamation point, 689it will be treated as a shell command. For example, defining 690"alias.new = !gitk --all --not ORIG_HEAD", the invocation 691"git new" is equivalent to running the shell command 692"gitk --all --not ORIG_HEAD". Note that shell commands will be 693executed from the top-level directory of a repository, which may 694not necessarily be the current directory. 695'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix' 696from the original current directory. See linkgit:git-rev-parse[1]. 697 698am.keepcr:: 699 If true, git-am will call git-mailsplit for patches in mbox format 700 with parameter '--keep-cr'. In this case git-mailsplit will 701 not remove `\r` from lines ending with `\r\n`. Can be overridden 702 by giving '--no-keep-cr' from the command line. 703 See linkgit:git-am[1], linkgit:git-mailsplit[1]. 704 705apply.ignorewhitespace:: 706 When set to 'change', tells 'git apply' to ignore changes in 707 whitespace, in the same way as the '--ignore-space-change' 708 option. 709 When set to one of: no, none, never, false tells 'git apply' to 710 respect all whitespace differences. 711 See linkgit:git-apply[1]. 712 713apply.whitespace:: 714 Tells 'git apply' how to handle whitespaces, in the same way 715 as the '--whitespace' option. See linkgit:git-apply[1]. 716 717branch.autosetupmerge:: 718 Tells 'git branch' and 'git checkout' to set up new branches 719 so that linkgit:git-pull[1] will appropriately merge from the 720 starting point branch. Note that even if this option is not set, 721 this behavior can be chosen per-branch using the `--track` 722 and `--no-track` options. The valid settings are: `false` -- no 723 automatic setup is done; `true` -- automatic setup is done when the 724 starting point is a remote-tracking branch; `always` -- 725 automatic setup is done when the starting point is either a 726 local branch or remote-tracking 727 branch. This option defaults to true. 728 729branch.autosetuprebase:: 730 When a new branch is created with 'git branch' or 'git checkout' 731 that tracks another branch, this variable tells Git to set 732 up pull to rebase instead of merge (see "branch.<name>.rebase"). 733 When `never`, rebase is never automatically set to true. 734 When `local`, rebase is set to true for tracked branches of 735 other local branches. 736 When `remote`, rebase is set to true for tracked branches of 737 remote-tracking branches. 738 When `always`, rebase will be set to true for all tracking 739 branches. 740 See "branch.autosetupmerge" for details on how to set up a 741 branch to track another branch. 742 This option defaults to never. 743 744branch.<name>.remote:: 745 When on branch <name>, it tells 'git fetch' and 'git push' 746 which remote to fetch from/push to. The remote to push to 747 may be overridden with `remote.pushdefault` (for all branches). 748 The remote to push to, for the current branch, may be further 749 overridden by `branch.<name>.pushremote`. If no remote is 750 configured, or if you are not on any branch, it defaults to 751 `origin` for fetching and `remote.pushdefault` for pushing. 752 Additionally, `.` (a period) is the current local repository 753 (a dot-repository), see `branch.<name>.merge`'s final note below. 754 755branch.<name>.pushremote:: 756 When on branch <name>, it overrides `branch.<name>.remote` for 757 pushing. It also overrides `remote.pushdefault` for pushing 758 from branch <name>. When you pull from one place (e.g. your 759 upstream) and push to another place (e.g. your own publishing 760 repository), you would want to set `remote.pushdefault` to 761 specify the remote to push to for all branches, and use this 762 option to override it for a specific branch. 763 764branch.<name>.merge:: 765 Defines, together with branch.<name>.remote, the upstream branch 766 for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which 767 branch to merge and can also affect 'git push' (see push.default). 768 When in branch <name>, it tells 'git fetch' the default 769 refspec to be marked for merging in FETCH_HEAD. The value is 770 handled like the remote part of a refspec, and must match a 771 ref which is fetched from the remote given by 772 "branch.<name>.remote". 773 The merge information is used by 'git pull' (which at first calls 774 'git fetch') to lookup the default branch for merging. Without 775 this option, 'git pull' defaults to merge the first refspec fetched. 776 Specify multiple values to get an octopus merge. 777 If you wish to setup 'git pull' so that it merges into <name> from 778 another branch in the local repository, you can point 779 branch.<name>.merge to the desired branch, and use the relative path 780 setting `.` (a period) for branch.<name>.remote. 781 782branch.<name>.mergeoptions:: 783 Sets default options for merging into branch <name>. The syntax and 784 supported options are the same as those of linkgit:git-merge[1], but 785 option values containing whitespace characters are currently not 786 supported. 787 788branch.<name>.rebase:: 789 When true, rebase the branch <name> on top of the fetched branch, 790 instead of merging the default branch from the default remote when 791 "git pull" is run. See "pull.rebase" for doing this in a non 792 branch-specific manner. 793+ 794 When preserve, also pass `--preserve-merges` along to 'git rebase' 795 so that locally committed merge commits will not be flattened 796 by running 'git pull'. 797+ 798*NOTE*: this is a possibly dangerous operation; do *not* use 799it unless you understand the implications (see linkgit:git-rebase[1] 800for details). 801 802branch.<name>.description:: 803 Branch description, can be edited with 804 `git branch --edit-description`. Branch description is 805 automatically added in the format-patch cover letter or 806 request-pull summary. 807 808browser.<tool>.cmd:: 809 Specify the command to invoke the specified browser. The 810 specified command is evaluated in shell with the URLs passed 811 as arguments. (See linkgit:git-web{litdd}browse[1].) 812 813browser.<tool>.path:: 814 Override the path for the given tool that may be used to 815 browse HTML help (see '-w' option in linkgit:git-help[1]) or a 816 working repository in gitweb (see linkgit:git-instaweb[1]). 817 818clean.requireForce:: 819 A boolean to make git-clean do nothing unless given -f, 820 -i or -n. Defaults to true. 821 822color.branch:: 823 A boolean to enable/disable color in the output of 824 linkgit:git-branch[1]. May be set to `always`, 825 `false` (or `never`) or `auto` (or `true`), in which case colors are used 826 only when the output is to a terminal. Defaults to false. 827 828color.branch.<slot>:: 829 Use customized color for branch coloration. `<slot>` is one of 830 `current` (the current branch), `local` (a local branch), 831 `remote` (a remote-tracking branch in refs/remotes/), 832 `upstream` (upstream tracking branch), `plain` (other 833 refs). 834+ 835The value for these configuration variables is a list of colors (at most 836two) and attributes (at most one), separated by spaces. The colors 837accepted are `normal`, `black`, `red`, `green`, `yellow`, `blue`, 838`magenta`, `cyan` and `white`; the attributes are `bold`, `dim`, `ul`, 839`blink` and `reverse`. The first color given is the foreground; the 840second is the background. The position of the attribute, if any, 841doesn't matter. 842 843color.diff:: 844 Whether to use ANSI escape sequences to add color to patches. 845 If this is set to `always`, linkgit:git-diff[1], 846 linkgit:git-log[1], and linkgit:git-show[1] will use color 847 for all patches. If it is set to `true` or `auto`, those 848 commands will only use color when output is to the terminal. 849 Defaults to false. 850+ 851This does not affect linkgit:git-format-patch[1] or the 852'git-diff-{asterisk}' plumbing commands. Can be overridden on the 853command line with the `--color[=<when>]` option. 854 855color.diff.<slot>:: 856 Use customized color for diff colorization. `<slot>` specifies 857 which part of the patch to use the specified color, and is one 858 of `plain` (context text), `meta` (metainformation), `frag` 859 (hunk header), 'func' (function in hunk header), `old` (removed lines), 860 `new` (added lines), `commit` (commit headers), or `whitespace` 861 (highlighting whitespace errors). The values of these variables may be 862 specified as in color.branch.<slot>. 863 864color.decorate.<slot>:: 865 Use customized color for 'git log --decorate' output. `<slot>` is one 866 of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local 867 branches, remote-tracking branches, tags, stash and HEAD, respectively. 868 869color.grep:: 870 When set to `always`, always highlight matches. When `false` (or 871 `never`), never. When set to `true` or `auto`, use color only 872 when the output is written to the terminal. Defaults to `false`. 873 874color.grep.<slot>:: 875 Use customized color for grep colorization. `<slot>` specifies which 876 part of the line to use the specified color, and is one of 877+ 878-- 879`context`;; 880 non-matching text in context lines (when using `-A`, `-B`, or `-C`) 881`filename`;; 882 filename prefix (when not using `-h`) 883`function`;; 884 function name lines (when using `-p`) 885`linenumber`;; 886 line number prefix (when using `-n`) 887`match`;; 888 matching text 889`selected`;; 890 non-matching text in selected lines 891`separator`;; 892 separators between fields on a line (`:`, `-`, and `=`) 893 and between hunks (`--`) 894-- 895+ 896The values of these variables may be specified as in color.branch.<slot>. 897 898color.interactive:: 899 When set to `always`, always use colors for interactive prompts 900 and displays (such as those used by "git-add --interactive" and 901 "git-clean --interactive"). When false (or `never`), never. 902 When set to `true` or `auto`, use colors only when the output is 903 to the terminal. Defaults to false. 904 905color.interactive.<slot>:: 906 Use customized color for 'git add --interactive' and 'git clean 907 --interactive' output. `<slot>` may be `prompt`, `header`, `help` 908 or `error`, for four distinct types of normal output from 909 interactive commands. The values of these variables may be 910 specified as in color.branch.<slot>. 911 912color.pager:: 913 A boolean to enable/disable colored output when the pager is in 914 use (default is true). 915 916color.showbranch:: 917 A boolean to enable/disable color in the output of 918 linkgit:git-show-branch[1]. May be set to `always`, 919 `false` (or `never`) or `auto` (or `true`), in which case colors are used 920 only when the output is to a terminal. Defaults to false. 921 922color.status:: 923 A boolean to enable/disable color in the output of 924 linkgit:git-status[1]. May be set to `always`, 925 `false` (or `never`) or `auto` (or `true`), in which case colors are used 926 only when the output is to a terminal. Defaults to false. 927 928color.status.<slot>:: 929 Use customized color for status colorization. `<slot>` is 930 one of `header` (the header text of the status message), 931 `added` or `updated` (files which are added but not committed), 932 `changed` (files which are changed but not added in the index), 933 `untracked` (files which are not tracked by Git), 934 `branch` (the current branch), or 935 `nobranch` (the color the 'no branch' warning is shown in, defaulting 936 to red). The values of these variables may be specified as in 937 color.branch.<slot>. 938 939color.ui:: 940 This variable determines the default value for variables such 941 as `color.diff` and `color.grep` that control the use of color 942 per command family. Its scope will expand as more commands learn 943 configuration to set a default for the `--color` option. Set it 944 to `false` or `never` if you prefer Git commands not to use 945 color unless enabled explicitly with some other configuration 946 or the `--color` option. Set it to `always` if you want all 947 output not intended for machine consumption to use color, to 948 `true` or `auto` (this is the default since Git 1.8.4) if you 949 want such output to use color when written to the terminal. 950 951column.ui:: 952 Specify whether supported commands should output in columns. 953 This variable consists of a list of tokens separated by spaces 954 or commas: 955+ 956These options control when the feature should be enabled 957(defaults to 'never'): 958+ 959-- 960`always`;; 961 always show in columns 962`never`;; 963 never show in columns 964`auto`;; 965 show in columns if the output is to the terminal 966-- 967+ 968These options control layout (defaults to 'column'). Setting any 969of these implies 'always' if none of 'always', 'never', or 'auto' are 970specified. 971+ 972-- 973`column`;; 974 fill columns before rows 975`row`;; 976 fill rows before columns 977`plain`;; 978 show in one column 979-- 980+ 981Finally, these options can be combined with a layout option (defaults 982to 'nodense'): 983+ 984-- 985`dense`;; 986 make unequal size columns to utilize more space 987`nodense`;; 988 make equal size columns 989-- 990 991column.branch:: 992 Specify whether to output branch listing in `git branch` in columns. 993 See `column.ui` for details. 994 995column.clean:: 996 Specify the layout when list items in `git clean -i`, which always 997 shows files and directories in columns. See `column.ui` for details. 998 999column.status::1000 Specify whether to output untracked files in `git status` in columns.1001 See `column.ui` for details.10021003column.tag::1004 Specify whether to output tag listing in `git tag` in columns.1005 See `column.ui` for details.10061007commit.cleanup::1008 This setting overrides the default of the `--cleanup` option in1009 `git commit`. See linkgit:git-commit[1] for details. Changing the1010 default can be useful when you always want to keep lines that begin1011 with comment character `#` in your log message, in which case you1012 would do `git config commit.cleanup whitespace` (note that you will1013 have to remove the help lines that begin with `#` in the commit log1014 template yourself, if you do this).10151016commit.gpgsign::10171018 A boolean to specify whether all commits should be GPG signed.1019 Use of this option when doing operations such as rebase can1020 result in a large number of commits being signed. It may be1021 convenient to use an agent to avoid typing your GPG passphrase1022 several times.10231024commit.status::1025 A boolean to enable/disable inclusion of status information in the1026 commit message template when using an editor to prepare the commit1027 message. Defaults to true.10281029commit.template::1030 Specify a file to use as the template for new commit messages.1031 "`~/`" is expanded to the value of `$HOME` and "`~user/`" to the1032 specified user's home directory.10331034credential.helper::1035 Specify an external helper to be called when a username or1036 password credential is needed; the helper may consult external1037 storage to avoid prompting the user for the credentials. See1038 linkgit:gitcredentials[7] for details.10391040credential.useHttpPath::1041 When acquiring credentials, consider the "path" component of an http1042 or https URL to be important. Defaults to false. See1043 linkgit:gitcredentials[7] for more information.10441045credential.username::1046 If no username is set for a network authentication, use this username1047 by default. See credential.<context>.* below, and1048 linkgit:gitcredentials[7].10491050credential.<url>.*::1051 Any of the credential.* options above can be applied selectively to1052 some credentials. For example "credential.https://example.com.username"1053 would set the default username only for https connections to1054 example.com. See linkgit:gitcredentials[7] for details on how URLs are1055 matched.10561057include::diff-config.txt[]10581059difftool.<tool>.path::1060 Override the path for the given tool. This is useful in case1061 your tool is not in the PATH.10621063difftool.<tool>.cmd::1064 Specify the command to invoke the specified diff tool.1065 The specified command is evaluated in shell with the following1066 variables available: 'LOCAL' is set to the name of the temporary1067 file containing the contents of the diff pre-image and 'REMOTE'1068 is set to the name of the temporary file containing the contents1069 of the diff post-image.10701071difftool.prompt::1072 Prompt before each invocation of the diff tool.10731074fetch.recurseSubmodules::1075 This option can be either set to a boolean value or to 'on-demand'.1076 Setting it to a boolean changes the behavior of fetch and pull to1077 unconditionally recurse into submodules when set to true or to not1078 recurse at all when set to false. When set to 'on-demand' (the default1079 value), fetch and pull will only recurse into a populated submodule1080 when its superproject retrieves a commit that updates the submodule's1081 reference.10821083fetch.fsckObjects::1084 If it is set to true, git-fetch-pack will check all fetched1085 objects. It will abort in the case of a malformed object or a1086 broken link. The result of an abort are only dangling objects.1087 Defaults to false. If not set, the value of `transfer.fsckObjects`1088 is used instead.10891090fetch.unpackLimit::1091 If the number of objects fetched over the Git native1092 transfer is below this1093 limit, then the objects will be unpacked into loose object1094 files. However if the number of received objects equals or1095 exceeds this limit then the received pack will be stored as1096 a pack, after adding any missing delta bases. Storing the1097 pack from a push can make the push operation complete faster,1098 especially on slow filesystems. If not set, the value of1099 `transfer.unpackLimit` is used instead.11001101fetch.prune::1102 If true, fetch will automatically behave as if the `--prune`1103 option was given on the command line. See also `remote.<name>.prune`.11041105format.attach::1106 Enable multipart/mixed attachments as the default for1107 'format-patch'. The value can also be a double quoted string1108 which will enable attachments as the default and set the1109 value as the boundary. See the --attach option in1110 linkgit:git-format-patch[1].11111112format.numbered::1113 A boolean which can enable or disable sequence numbers in patch1114 subjects. It defaults to "auto" which enables it only if there1115 is more than one patch. It can be enabled or disabled for all1116 messages by setting it to "true" or "false". See --numbered1117 option in linkgit:git-format-patch[1].11181119format.headers::1120 Additional email headers to include in a patch to be submitted1121 by mail. See linkgit:git-format-patch[1].11221123format.to::1124format.cc::1125 Additional recipients to include in a patch to be submitted1126 by mail. See the --to and --cc options in1127 linkgit:git-format-patch[1].11281129format.subjectprefix::1130 The default for format-patch is to output files with the '[PATCH]'1131 subject prefix. Use this variable to change that prefix.11321133format.signature::1134 The default for format-patch is to output a signature containing1135 the Git version number. Use this variable to change that default.1136 Set this variable to the empty string ("") to suppress1137 signature generation.11381139format.signaturefile::1140 Works just like format.signature except the contents of the1141 file specified by this variable will be used as the signature.11421143format.suffix::1144 The default for format-patch is to output files with the suffix1145 `.patch`. Use this variable to change that suffix (make sure to1146 include the dot if you want it).11471148format.pretty::1149 The default pretty format for log/show/whatchanged command,1150 See linkgit:git-log[1], linkgit:git-show[1],1151 linkgit:git-whatchanged[1].11521153format.thread::1154 The default threading style for 'git format-patch'. Can be1155 a boolean value, or `shallow` or `deep`. `shallow` threading1156 makes every mail a reply to the head of the series,1157 where the head is chosen from the cover letter, the1158 `--in-reply-to`, and the first patch mail, in this order.1159 `deep` threading makes every mail a reply to the previous one.1160 A true boolean value is the same as `shallow`, and a false1161 value disables threading.11621163format.signoff::1164 A boolean value which lets you enable the `-s/--signoff` option of1165 format-patch by default. *Note:* Adding the Signed-off-by: line to a1166 patch should be a conscious act and means that you certify you have1167 the rights to submit this work under the same open source license.1168 Please see the 'SubmittingPatches' document for further discussion.11691170format.coverLetter::1171 A boolean that controls whether to generate a cover-letter when1172 format-patch is invoked, but in addition can be set to "auto", to1173 generate a cover-letter only when there's more than one patch.11741175filter.<driver>.clean::1176 The command which is used to convert the content of a worktree1177 file to a blob upon checkin. See linkgit:gitattributes[5] for1178 details.11791180filter.<driver>.smudge::1181 The command which is used to convert the content of a blob1182 object to a worktree file upon checkout. See1183 linkgit:gitattributes[5] for details.11841185gc.aggressiveDepth::1186 The depth parameter used in the delta compression1187 algorithm used by 'git gc --aggressive'. This defaults1188 to 250.11891190gc.aggressiveWindow::1191 The window size parameter used in the delta compression1192 algorithm used by 'git gc --aggressive'. This defaults1193 to 250.11941195gc.auto::1196 When there are approximately more than this many loose1197 objects in the repository, `git gc --auto` will pack them.1198 Some Porcelain commands use this command to perform a1199 light-weight garbage collection from time to time. The1200 default value is 6700. Setting this to 0 disables it.12011202gc.autopacklimit::1203 When there are more than this many packs that are not1204 marked with `*.keep` file in the repository, `git gc1205 --auto` consolidates them into one larger pack. The1206 default value is 50. Setting this to 0 disables it.12071208gc.autodetach::1209 Make `git gc --auto` return immediately andrun in background1210 if the system supports it. Default is true.12111212gc.packrefs::1213 Running `git pack-refs` in a repository renders it1214 unclonable by Git versions prior to 1.5.1.2 over dumb1215 transports such as HTTP. This variable determines whether1216 'git gc' runs `git pack-refs`. This can be set to `notbare`1217 to enable it within all non-bare repos or it can be set to a1218 boolean value. The default is `true`.12191220gc.pruneexpire::1221 When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.1222 Override the grace period with this config variable. The value1223 "now" may be used to disable this grace period and always prune1224 unreachable objects immediately.12251226gc.reflogexpire::1227gc.<pattern>.reflogexpire::1228 'git reflog expire' removes reflog entries older than1229 this time; defaults to 90 days. With "<pattern>" (e.g.1230 "refs/stash") in the middle the setting applies only to1231 the refs that match the <pattern>.12321233gc.reflogexpireunreachable::1234gc.<ref>.reflogexpireunreachable::1235 'git reflog expire' removes reflog entries older than1236 this time and are not reachable from the current tip;1237 defaults to 30 days. With "<pattern>" (e.g. "refs/stash")1238 in the middle, the setting applies only to the refs that1239 match the <pattern>.12401241gc.rerereresolved::1242 Records of conflicted merge you resolved earlier are1243 kept for this many days when 'git rerere gc' is run.1244 The default is 60 days. See linkgit:git-rerere[1].12451246gc.rerereunresolved::1247 Records of conflicted merge you have not resolved are1248 kept for this many days when 'git rerere gc' is run.1249 The default is 15 days. See linkgit:git-rerere[1].12501251gitcvs.commitmsgannotation::1252 Append this string to each commit message. Set to empty string1253 to disable this feature. Defaults to "via git-CVS emulator".12541255gitcvs.enabled::1256 Whether the CVS server interface is enabled for this repository.1257 See linkgit:git-cvsserver[1].12581259gitcvs.logfile::1260 Path to a log file where the CVS server interface well... logs1261 various stuff. See linkgit:git-cvsserver[1].12621263gitcvs.usecrlfattr::1264 If true, the server will look up the end-of-line conversion1265 attributes for files to determine the '-k' modes to use. If1266 the attributes force Git to treat a file as text,1267 the '-k' mode will be left blank so CVS clients will1268 treat it as text. If they suppress text conversion, the file1269 will be set with '-kb' mode, which suppresses any newline munging1270 the client might otherwise do. If the attributes do not allow1271 the file type to be determined, then 'gitcvs.allbinary' is1272 used. See linkgit:gitattributes[5].12731274gitcvs.allbinary::1275 This is used if 'gitcvs.usecrlfattr' does not resolve1276 the correct '-kb' mode to use. If true, all1277 unresolved files are sent to the client in1278 mode '-kb'. This causes the client to treat them1279 as binary files, which suppresses any newline munging it1280 otherwise might do. Alternatively, if it is set to "guess",1281 then the contents of the file are examined to decide if1282 it is binary, similar to 'core.autocrlf'.12831284gitcvs.dbname::1285 Database used by git-cvsserver to cache revision information1286 derived from the Git repository. The exact meaning depends on the1287 used database driver, for SQLite (which is the default driver) this1288 is a filename. Supports variable substitution (see1289 linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).1290 Default: '%Ggitcvs.%m.sqlite'12911292gitcvs.dbdriver::1293 Used Perl DBI driver. You can specify any available driver1294 for this here, but it might not work. git-cvsserver is tested1295 with 'DBD::SQLite', reported to work with 'DBD::Pg', and1296 reported *not* to work with 'DBD::mysql'. Experimental feature.1297 May not contain double colons (`:`). Default: 'SQLite'.1298 See linkgit:git-cvsserver[1].12991300gitcvs.dbuser, gitcvs.dbpass::1301 Database user and password. Only useful if setting 'gitcvs.dbdriver',1302 since SQLite has no concept of database users and/or passwords.1303 'gitcvs.dbuser' supports variable substitution (see1304 linkgit:git-cvsserver[1] for details).13051306gitcvs.dbTableNamePrefix::1307 Database table name prefix. Prepended to the names of any1308 database tables used, allowing a single database to be used1309 for several repositories. Supports variable substitution (see1310 linkgit:git-cvsserver[1] for details). Any non-alphabetic1311 characters will be replaced with underscores.13121313All gitcvs variables except for 'gitcvs.usecrlfattr' and1314'gitcvs.allbinary' can also be specified as1315'gitcvs.<access_method>.<varname>' (where 'access_method'1316is one of "ext" and "pserver") to make them apply only for the given1317access method.13181319gitweb.category::1320gitweb.description::1321gitweb.owner::1322gitweb.url::1323 See linkgit:gitweb[1] for description.13241325gitweb.avatar::1326gitweb.blame::1327gitweb.grep::1328gitweb.highlight::1329gitweb.patches::1330gitweb.pickaxe::1331gitweb.remote_heads::1332gitweb.showsizes::1333gitweb.snapshot::1334 See linkgit:gitweb.conf[5] for description.13351336grep.lineNumber::1337 If set to true, enable '-n' option by default.13381339grep.patternType::1340 Set the default matching behavior. Using a value of 'basic', 'extended',1341 'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',1342 '--fixed-strings', or '--perl-regexp' option accordingly, while the1343 value 'default' will return to the default matching behavior.13441345grep.extendedRegexp::1346 If set to true, enable '--extended-regexp' option by default. This1347 option is ignored when the 'grep.patternType' option is set to a value1348 other than 'default'.13491350gpg.program::1351 Use this custom program instead of "gpg" found on $PATH when1352 making or verifying a PGP signature. The program must support the1353 same command-line interface as GPG, namely, to verify a detached1354 signature, "gpg --verify $file - <$signature" is run, and the1355 program is expected to signal a good signature by exiting with1356 code 0, and to generate an ascii-armored detached signature, the1357 standard input of "gpg -bsau $key" is fed with the contents to be1358 signed, and the program is expected to send the result to its1359 standard output.13601361gui.commitmsgwidth::1362 Defines how wide the commit message window is in the1363 linkgit:git-gui[1]. "75" is the default.13641365gui.diffcontext::1366 Specifies how many context lines should be used in calls to diff1367 made by the linkgit:git-gui[1]. The default is "5".13681369gui.displayuntracked::1370 Determines if linkgit::git-gui[1] shows untracked files1371 in the file list. The default is "true".13721373gui.encoding::1374 Specifies the default encoding to use for displaying of1375 file contents in linkgit:git-gui[1] and linkgit:gitk[1].1376 It can be overridden by setting the 'encoding' attribute1377 for relevant files (see linkgit:gitattributes[5]).1378 If this option is not set, the tools default to the1379 locale encoding.13801381gui.matchtrackingbranch::1382 Determines if new branches created with linkgit:git-gui[1] should1383 default to tracking remote branches with matching names or1384 not. Default: "false".13851386gui.newbranchtemplate::1387 Is used as suggested name when creating new branches using the1388 linkgit:git-gui[1].13891390gui.pruneduringfetch::1391 "true" if linkgit:git-gui[1] should prune remote-tracking branches when1392 performing a fetch. The default value is "false".13931394gui.trustmtime::1395 Determines if linkgit:git-gui[1] should trust the file modification1396 timestamp or not. By default the timestamps are not trusted.13971398gui.spellingdictionary::1399 Specifies the dictionary used for spell checking commit messages in1400 the linkgit:git-gui[1]. When set to "none" spell checking is turned1401 off.14021403gui.fastcopyblame::1404 If true, 'git gui blame' uses `-C` instead of `-C -C` for original1405 location detection. It makes blame significantly faster on huge1406 repositories at the expense of less thorough copy detection.14071408gui.copyblamethreshold::1409 Specifies the threshold to use in 'git gui blame' original location1410 detection, measured in alphanumeric characters. See the1411 linkgit:git-blame[1] manual for more information on copy detection.14121413gui.blamehistoryctx::1414 Specifies the radius of history context in days to show in1415 linkgit:gitk[1] for the selected commit, when the `Show History1416 Context` menu item is invoked from 'git gui blame'. If this1417 variable is set to zero, the whole history is shown.14181419guitool.<name>.cmd::1420 Specifies the shell command line to execute when the corresponding item1421 of the linkgit:git-gui[1] `Tools` menu is invoked. This option is1422 mandatory for every tool. The command is executed from the root of1423 the working directory, and in the environment it receives the name of1424 the tool as 'GIT_GUITOOL', the name of the currently selected file as1425 'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if1426 the head is detached, 'CUR_BRANCH' is empty).14271428guitool.<name>.needsfile::1429 Run the tool only if a diff is selected in the GUI. It guarantees1430 that 'FILENAME' is not empty.14311432guitool.<name>.noconsole::1433 Run the command silently, without creating a window to display its1434 output.14351436guitool.<name>.norescan::1437 Don't rescan the working directory for changes after the tool1438 finishes execution.14391440guitool.<name>.confirm::1441 Show a confirmation dialog before actually running the tool.14421443guitool.<name>.argprompt::1444 Request a string argument from the user, and pass it to the tool1445 through the 'ARGS' environment variable. Since requesting an1446 argument implies confirmation, the 'confirm' option has no effect1447 if this is enabled. If the option is set to 'true', 'yes', or '1',1448 the dialog uses a built-in generic prompt; otherwise the exact1449 value of the variable is used.14501451guitool.<name>.revprompt::1452 Request a single valid revision from the user, and set the1453 'REVISION' environment variable. In other aspects this option1454 is similar to 'argprompt', and can be used together with it.14551456guitool.<name>.revunmerged::1457 Show only unmerged branches in the 'revprompt' subdialog.1458 This is useful for tools similar to merge or rebase, but not1459 for things like checkout or reset.14601461guitool.<name>.title::1462 Specifies the title to use for the prompt dialog. The default1463 is the tool name.14641465guitool.<name>.prompt::1466 Specifies the general prompt string to display at the top of1467 the dialog, before subsections for 'argprompt' and 'revprompt'.1468 The default value includes the actual command.14691470help.browser::1471 Specify the browser that will be used to display help in the1472 'web' format. See linkgit:git-help[1].14731474help.format::1475 Override the default help format used by linkgit:git-help[1].1476 Values 'man', 'info', 'web' and 'html' are supported. 'man' is1477 the default. 'web' and 'html' are the same.14781479help.autocorrect::1480 Automatically correct and execute mistyped commands after1481 waiting for the given number of deciseconds (0.1 sec). If more1482 than one command can be deduced from the entered text, nothing1483 will be executed. If the value of this option is negative,1484 the corrected command will be executed immediately. If the1485 value is 0 - the command will be just shown but not executed.1486 This is the default.14871488help.htmlpath::1489 Specify the path where the HTML documentation resides. File system paths1490 and URLs are supported. HTML pages will be prefixed with this path when1491 help is displayed in the 'web' format. This defaults to the documentation1492 path of your Git installation.14931494http.proxy::1495 Override the HTTP proxy, normally configured using the 'http_proxy',1496 'https_proxy', and 'all_proxy' environment variables (see1497 `curl(1)`). This can be overridden on a per-remote basis; see1498 remote.<name>.proxy14991500http.cookiefile::1501 File containing previously stored cookie lines which should be used1502 in the Git http session, if they match the server. The file format1503 of the file to read cookies from should be plain HTTP headers or1504 the Netscape/Mozilla cookie file format (see linkgit:curl[1]).1505 NOTE that the file specified with http.cookiefile is only used as1506 input unless http.saveCookies is set.15071508http.savecookies::1509 If set, store cookies received during requests to the file specified by1510 http.cookiefile. Has no effect if http.cookiefile is unset.15111512http.sslVerify::1513 Whether to verify the SSL certificate when fetching or pushing1514 over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment1515 variable.15161517http.sslCert::1518 File containing the SSL certificate when fetching or pushing1519 over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment1520 variable.15211522http.sslKey::1523 File containing the SSL private key when fetching or pushing1524 over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment1525 variable.15261527http.sslCertPasswordProtected::1528 Enable Git's password prompt for the SSL certificate. Otherwise1529 OpenSSL will prompt the user, possibly many times, if the1530 certificate or private key is encrypted. Can be overridden by the1531 'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.15321533http.sslCAInfo::1534 File containing the certificates to verify the peer with when1535 fetching or pushing over HTTPS. Can be overridden by the1536 'GIT_SSL_CAINFO' environment variable.15371538http.sslCAPath::1539 Path containing files with the CA certificates to verify the peer1540 with when fetching or pushing over HTTPS. Can be overridden1541 by the 'GIT_SSL_CAPATH' environment variable.15421543http.sslTry::1544 Attempt to use AUTH SSL/TLS and encrypted data transfers1545 when connecting via regular FTP protocol. This might be needed1546 if the FTP server requires it for security reasons or you wish1547 to connect securely whenever remote FTP server supports it.1548 Default is false since it might trigger certificate verification1549 errors on misconfigured servers.15501551http.maxRequests::1552 How many HTTP requests to launch in parallel. Can be overridden1553 by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.15541555http.minSessions::1556 The number of curl sessions (counted across slots) to be kept across1557 requests. They will not be ended with curl_easy_cleanup() until1558 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this1559 value will be capped at 1. Defaults to 1.15601561http.postBuffer::1562 Maximum size in bytes of the buffer used by smart HTTP1563 transports when POSTing data to the remote system.1564 For requests larger than this buffer size, HTTP/1.1 and1565 Transfer-Encoding: chunked is used to avoid creating a1566 massive pack file locally. Default is 1 MiB, which is1567 sufficient for most requests.15681569http.lowSpeedLimit, http.lowSpeedTime::1570 If the HTTP transfer speed is less than 'http.lowSpeedLimit'1571 for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.1572 Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and1573 'GIT_HTTP_LOW_SPEED_TIME' environment variables.15741575http.noEPSV::1576 A boolean which disables using of EPSV ftp command by curl.1577 This can helpful with some "poor" ftp servers which don't1578 support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'1579 environment variable. Default is false (curl will use EPSV).15801581http.useragent::1582 The HTTP USER_AGENT string presented to an HTTP server. The default1583 value represents the version of the client Git such as git/1.7.1.1584 This option allows you to override this value to a more common value1585 such as Mozilla/4.0. This may be necessary, for instance, if1586 connecting through a firewall that restricts HTTP connections to a set1587 of common USER_AGENT strings (but not including those like git/1.7.1).1588 Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.15891590http.<url>.*::1591 Any of the http.* options above can be applied selectively to some urls.1592 For a config key to match a URL, each element of the config key is1593 compared to that of the URL, in the following order:1594+1595--1596. Scheme (e.g., `https` in `https://example.com/`). This field1597 must match exactly between the config key and the URL.15981599. Host/domain name (e.g., `example.com` in `https://example.com/`).1600 This field must match exactly between the config key and the URL.16011602. Port number (e.g., `8080` in `http://example.com:8080/`).1603 This field must match exactly between the config key and the URL.1604 Omitted port numbers are automatically converted to the correct1605 default for the scheme before matching.16061607. Path (e.g., `repo.git` in `https://example.com/repo.git`). The1608 path field of the config key must match the path field of the URL1609 either exactly or as a prefix of slash-delimited path elements. This means1610 a config key with path `foo/` matches URL path `foo/bar`. A prefix can only1611 match on a slash (`/`) boundary. Longer matches take precedence (so a config1612 key with path `foo/bar` is a better match to URL path `foo/bar` than a config1613 key with just path `foo/`).16141615. User name (e.g., `user` in `https://user@example.com/repo.git`). If1616 the config key has a user name it must match the user name in the1617 URL exactly. If the config key does not have a user name, that1618 config key will match a URL with any user name (including none),1619 but at a lower precedence than a config key with a user name.1620--1621+1622The list above is ordered by decreasing precedence; a URL that matches1623a config key's path is preferred to one that matches its user name. For example,1624if the URL is `https://user@example.com/foo/bar` a config key match of1625`https://example.com/foo` will be preferred over a config key match of1626`https://user@example.com`.1627+1628All URLs are normalized before attempting any matching (the password part,1629if embedded in the URL, is always ignored for matching purposes) so that1630equivalent urls that are simply spelled differently will match properly.1631Environment variable settings always override any matches. The urls that are1632matched against are those given directly to Git commands. This means any URLs1633visited as a result of a redirection do not participate in matching.16341635i18n.commitEncoding::1636 Character encoding the commit messages are stored in; Git itself1637 does not care per se, but this information is necessary e.g. when1638 importing commits from emails or in the gitk graphical history1639 browser (and possibly at other places in the future or in other1640 porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.16411642i18n.logOutputEncoding::1643 Character encoding the commit messages are converted to when1644 running 'git log' and friends.16451646imap::1647 The configuration variables in the 'imap' section are described1648 in linkgit:git-imap-send[1].16491650index.version::1651 Specify the version with which new index files should be1652 initialized. This does not affect existing repositories.16531654init.templatedir::1655 Specify the directory from which templates will be copied.1656 (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)16571658instaweb.browser::1659 Specify the program that will be used to browse your working1660 repository in gitweb. See linkgit:git-instaweb[1].16611662instaweb.httpd::1663 The HTTP daemon command-line to start gitweb on your working1664 repository. See linkgit:git-instaweb[1].16651666instaweb.local::1667 If true the web server started by linkgit:git-instaweb[1] will1668 be bound to the local IP (127.0.0.1).16691670instaweb.modulepath::1671 The default module path for linkgit:git-instaweb[1] to use1672 instead of /usr/lib/apache2/modules. Only used if httpd1673 is Apache.16741675instaweb.port::1676 The port number to bind the gitweb httpd to. See1677 linkgit:git-instaweb[1].16781679interactive.singlekey::1680 In interactive commands, allow the user to provide one-letter1681 input with a single key (i.e., without hitting enter).1682 Currently this is used by the `--patch` mode of1683 linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],1684 linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this1685 setting is silently ignored if portable keystroke input1686 is not available; requires the Perl module Term::ReadKey.16871688log.abbrevCommit::1689 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1690 linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may1691 override this option with `--no-abbrev-commit`.16921693log.date::1694 Set the default date-time mode for the 'log' command.1695 Setting a value for log.date is similar to using 'git log''s1696 `--date` option. Possible values are `relative`, `local`,1697 `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]1698 for details.16991700log.decorate::1701 Print out the ref names of any commits that are shown by the log1702 command. If 'short' is specified, the ref name prefixes 'refs/heads/',1703 'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is1704 specified, the full ref name (including prefix) will be printed.1705 This is the same as the log commands '--decorate' option.17061707log.showroot::1708 If true, the initial commit will be shown as a big creation event.1709 This is equivalent to a diff against an empty tree.1710 Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which1711 normally hide the root commit will now show it. True by default.17121713log.mailmap::1714 If true, makes linkgit:git-log[1], linkgit:git-show[1], and1715 linkgit:git-whatchanged[1] assume `--use-mailmap`.17161717mailmap.file::1718 The location of an augmenting mailmap file. The default1719 mailmap, located in the root of the repository, is loaded1720 first, then the mailmap file pointed to by this variable.1721 The location of the mailmap file may be in a repository1722 subdirectory, or somewhere outside of the repository itself.1723 See linkgit:git-shortlog[1] and linkgit:git-blame[1].17241725mailmap.blob::1726 Like `mailmap.file`, but consider the value as a reference to a1727 blob in the repository. If both `mailmap.file` and1728 `mailmap.blob` are given, both are parsed, with entries from1729 `mailmap.file` taking precedence. In a bare repository, this1730 defaults to `HEAD:.mailmap`. In a non-bare repository, it1731 defaults to empty.17321733man.viewer::1734 Specify the programs that may be used to display help in the1735 'man' format. See linkgit:git-help[1].17361737man.<tool>.cmd::1738 Specify the command to invoke the specified man viewer. The1739 specified command is evaluated in shell with the man page1740 passed as argument. (See linkgit:git-help[1].)17411742man.<tool>.path::1743 Override the path for the given tool that may be used to1744 display help in the 'man' format. See linkgit:git-help[1].17451746include::merge-config.txt[]17471748mergetool.<tool>.path::1749 Override the path for the given tool. This is useful in case1750 your tool is not in the PATH.17511752mergetool.<tool>.cmd::1753 Specify the command to invoke the specified merge tool. The1754 specified command is evaluated in shell with the following1755 variables available: 'BASE' is the name of a temporary file1756 containing the common base of the files to be merged, if available;1757 'LOCAL' is the name of a temporary file containing the contents of1758 the file on the current branch; 'REMOTE' is the name of a temporary1759 file containing the contents of the file from the branch being1760 merged; 'MERGED' contains the name of the file to which the merge1761 tool should write the results of a successful merge.17621763mergetool.<tool>.trustExitCode::1764 For a custom merge command, specify whether the exit code of1765 the merge command can be used to determine whether the merge was1766 successful. If this is not set to true then the merge target file1767 timestamp is checked and the merge assumed to have been successful1768 if the file has been updated, otherwise the user is prompted to1769 indicate the success of the merge.17701771mergetool.meld.hasOutput::1772 Older versions of `meld` do not support the `--output` option.1773 Git will attempt to detect whether `meld` supports `--output`1774 by inspecting the output of `meld --help`. Configuring1775 `mergetool.meld.hasOutput` will make Git skip these checks and1776 use the configured value instead. Setting `mergetool.meld.hasOutput`1777 to `true` tells Git to unconditionally use the `--output` option,1778 and `false` avoids using `--output`.17791780mergetool.keepBackup::1781 After performing a merge, the original file with conflict markers1782 can be saved as a file with a `.orig` extension. If this variable1783 is set to `false` then this file is not preserved. Defaults to1784 `true` (i.e. keep the backup files).17851786mergetool.keepTemporaries::1787 When invoking a custom merge tool, Git uses a set of temporary1788 files to pass to the tool. If the tool returns an error and this1789 variable is set to `true`, then these temporary files will be1790 preserved, otherwise they will be removed after the tool has1791 exited. Defaults to `false`.17921793mergetool.writeToTemp::1794 Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of1795 conflicting files in the worktree by default. Git will attempt1796 to use a temporary directory for these files when set `true`.1797 Defaults to `false`.17981799mergetool.prompt::1800 Prompt before each invocation of the merge resolution program.18011802notes.displayRef::1803 The (fully qualified) refname from which to show notes when1804 showing commit messages. The value of this variable can be set1805 to a glob, in which case notes from all matching refs will be1806 shown. You may also specify this configuration variable1807 several times. A warning will be issued for refs that do not1808 exist, but a glob that does not match any refs is silently1809 ignored.1810+1811This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`1812environment variable, which must be a colon separated list of refs or1813globs.1814+1815The effective value of "core.notesRef" (possibly overridden by1816GIT_NOTES_REF) is also implicitly added to the list of refs to be1817displayed.18181819notes.rewrite.<command>::1820 When rewriting commits with <command> (currently `amend` or1821 `rebase`) and this variable is set to `true`, Git1822 automatically copies your notes from the original to the1823 rewritten commit. Defaults to `true`, but see1824 "notes.rewriteRef" below.18251826notes.rewriteMode::1827 When copying notes during a rewrite (see the1828 "notes.rewrite.<command>" option), determines what to do if1829 the target commit already has a note. Must be one of1830 `overwrite`, `concatenate`, or `ignore`. Defaults to1831 `concatenate`.1832+1833This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`1834environment variable.18351836notes.rewriteRef::1837 When copying notes during a rewrite, specifies the (fully1838 qualified) ref whose notes should be copied. The ref may be a1839 glob, in which case notes in all matching refs will be copied.1840 You may also specify this configuration several times.1841+1842Does not have a default value; you must configure this variable to1843enable note rewriting. Set it to `refs/notes/commits` to enable1844rewriting for the default commit notes.1845+1846This setting can be overridden with the `GIT_NOTES_REWRITE_REF`1847environment variable, which must be a colon separated list of refs or1848globs.18491850pack.window::1851 The size of the window used by linkgit:git-pack-objects[1] when no1852 window size is given on the command line. Defaults to 10.18531854pack.depth::1855 The maximum delta depth used by linkgit:git-pack-objects[1] when no1856 maximum depth is given on the command line. Defaults to 50.18571858pack.windowMemory::1859 The window memory size limit used by linkgit:git-pack-objects[1]1860 when no limit is given on the command line. The value can be1861 suffixed with "k", "m", or "g". Defaults to 0, meaning no1862 limit.18631864pack.compression::1865 An integer -1..9, indicating the compression level for objects1866 in a pack file. -1 is the zlib default. 0 means no1867 compression, and 1..9 are various speed/size tradeoffs, 9 being1868 slowest. If not set, defaults to core.compression. If that is1869 not set, defaults to -1, the zlib default, which is "a default1870 compromise between speed and compression (currently equivalent1871 to level 6)."1872+1873Note that changing the compression level will not automatically recompress1874all existing objects. You can force recompression by passing the -F option1875to linkgit:git-repack[1].18761877pack.deltaCacheSize::1878 The maximum memory in bytes used for caching deltas in1879 linkgit:git-pack-objects[1] before writing them out to a pack.1880 This cache is used to speed up the writing object phase by not1881 having to recompute the final delta result once the best match1882 for all objects is found. Repacking large repositories on machines1883 which are tight with memory might be badly impacted by this though,1884 especially if this cache pushes the system into swapping.1885 A value of 0 means no limit. The smallest size of 1 byte may be1886 used to virtually disable this cache. Defaults to 256 MiB.18871888pack.deltaCacheLimit::1889 The maximum size of a delta, that is cached in1890 linkgit:git-pack-objects[1]. This cache is used to speed up the1891 writing object phase by not having to recompute the final delta1892 result once the best match for all objects is found. Defaults to 1000.18931894pack.threads::1895 Specifies the number of threads to spawn when searching for best1896 delta matches. This requires that linkgit:git-pack-objects[1]1897 be compiled with pthreads otherwise this option is ignored with a1898 warning. This is meant to reduce packing time on multiprocessor1899 machines. The required amount of memory for the delta search window1900 is however multiplied by the number of threads.1901 Specifying 0 will cause Git to auto-detect the number of CPU's1902 and set the number of threads accordingly.19031904pack.indexVersion::1905 Specify the default pack index version. Valid values are 1 for1906 legacy pack index used by Git versions prior to 1.5.2, and 2 for1907 the new pack index with capabilities for packs larger than 4 GB1908 as well as proper protection against the repacking of corrupted1909 packs. Version 2 is the default. Note that version 2 is enforced1910 and this config option ignored whenever the corresponding pack is1911 larger than 2 GB.1912+1913If you have an old Git that does not understand the version 2 `*.idx` file,1914cloning or fetching over a non native protocol (e.g. "http" and "rsync")1915that will copy both `*.pack` file and corresponding `*.idx` file from the1916other side may give you a repository that cannot be accessed with your1917older version of Git. If the `*.pack` file is smaller than 2 GB, however,1918you can use linkgit:git-index-pack[1] on the *.pack file to regenerate1919the `*.idx` file.19201921pack.packSizeLimit::1922 The maximum size of a pack. This setting only affects1923 packing to a file when repacking, i.e. the git:// protocol1924 is unaffected. It can be overridden by the `--max-pack-size`1925 option of linkgit:git-repack[1]. The minimum size allowed is1926 limited to 1 MiB. The default is unlimited.1927 Common unit suffixes of 'k', 'm', or 'g' are1928 supported.19291930pack.useBitmaps::1931 When true, git will use pack bitmaps (if available) when packing1932 to stdout (e.g., during the server side of a fetch). Defaults to1933 true. You should not generally need to turn this off unless1934 you are debugging pack bitmaps.19351936pack.writebitmaps::1937 This is a deprecated synonym for `repack.writeBitmaps`.19381939pack.writeBitmapHashCache::1940 When true, git will include a "hash cache" section in the bitmap1941 index (if one is written). This cache can be used to feed git's1942 delta heuristics, potentially leading to better deltas between1943 bitmapped and non-bitmapped objects (e.g., when serving a fetch1944 between an older, bitmapped pack and objects that have been1945 pushed since the last gc). The downside is that it consumes 41946 bytes per object of disk space, and that JGit's bitmap1947 implementation does not understand it, causing it to complain if1948 Git and JGit are used on the same repository. Defaults to false.19491950pager.<cmd>::1951 If the value is boolean, turns on or off pagination of the1952 output of a particular Git subcommand when writing to a tty.1953 Otherwise, turns on pagination for the subcommand using the1954 pager specified by the value of `pager.<cmd>`. If `--paginate`1955 or `--no-pager` is specified on the command line, it takes1956 precedence over this option. To disable pagination for all1957 commands, set `core.pager` or `GIT_PAGER` to `cat`.19581959pretty.<name>::1960 Alias for a --pretty= format string, as specified in1961 linkgit:git-log[1]. Any aliases defined here can be used just1962 as the built-in pretty formats could. For example,1963 running `git config pretty.changelog "format:* %H %s"`1964 would cause the invocation `git log --pretty=changelog`1965 to be equivalent to running `git log "--pretty=format:* %H %s"`.1966 Note that an alias with the same name as a built-in format1967 will be silently ignored.19681969pull.ff::1970 By default, Git does not create an extra merge commit when merging1971 a commit that is a descendant of the current commit. Instead, the1972 tip of the current branch is fast-forwarded. When set to `false`,1973 this variable tells Git to create an extra merge commit in such1974 a case (equivalent to giving the `--no-ff` option from the command1975 line). When set to `only`, only such fast-forward merges are1976 allowed (equivalent to giving the `--ff-only` option from the1977 command line).19781979pull.rebase::1980 When true, rebase branches on top of the fetched branch, instead1981 of merging the default branch from the default remote when "git1982 pull" is run. See "branch.<name>.rebase" for setting this on a1983 per-branch basis.1984+1985 When preserve, also pass `--preserve-merges` along to 'git rebase'1986 so that locally committed merge commits will not be flattened1987 by running 'git pull'.1988+1989*NOTE*: this is a possibly dangerous operation; do *not* use1990it unless you understand the implications (see linkgit:git-rebase[1]1991for details).19921993pull.octopus::1994 The default merge strategy to use when pulling multiple branches1995 at once.19961997pull.twohead::1998 The default merge strategy to use when pulling a single branch.19992000push.default::2001 Defines the action `git push` should take if no refspec is2002 explicitly given. Different values are well-suited for2003 specific workflows; for instance, in a purely central workflow2004 (i.e. the fetch source is equal to the push destination),2005 `upstream` is probably what you want. Possible values are:2006+2007--20082009* `nothing` - do not push anything (error out) unless a refspec is2010 explicitly given. This is primarily meant for people who want to2011 avoid mistakes by always being explicit.20122013* `current` - push the current branch to update a branch with the same2014 name on the receiving end. Works in both central and non-central2015 workflows.20162017* `upstream` - push the current branch back to the branch whose2018 changes are usually integrated into the current branch (which is2019 called `@{upstream}`). This mode only makes sense if you are2020 pushing to the same repository you would normally pull from2021 (i.e. central workflow).20222023* `simple` - in centralized workflow, work like `upstream` with an2024 added safety to refuse to push if the upstream branch's name is2025 different from the local one.2026+2027When pushing to a remote that is different from the remote you normally2028pull from, work as `current`. This is the safest option and is suited2029for beginners.2030+2031This mode has become the default in Git 2.0.20322033* `matching` - push all branches having the same name on both ends.2034 This makes the repository you are pushing to remember the set of2035 branches that will be pushed out (e.g. if you always push 'maint'2036 and 'master' there and no other branches, the repository you push2037 to will have these two branches, and your local 'maint' and2038 'master' will be pushed there).2039+2040To use this mode effectively, you have to make sure _all_ the2041branches you would push out are ready to be pushed out before2042running 'git push', as the whole point of this mode is to allow you2043to push all of the branches in one go. If you usually finish work2044on only one branch and push out the result, while other branches are2045unfinished, this mode is not for you. Also this mode is not2046suitable for pushing into a shared central repository, as other2047people may add new branches there, or update the tip of existing2048branches outside your control.2049+2050This used to be the default, but not since Git 2.0 (`simple` is the2051new default).20522053--20542055rebase.stat::2056 Whether to show a diffstat of what changed upstream since the last2057 rebase. False by default.20582059rebase.autosquash::2060 If set to true enable '--autosquash' option by default.20612062rebase.autostash::2063 When set to true, automatically create a temporary stash2064 before the operation begins, and apply it after the operation2065 ends. This means that you can run rebase on a dirty worktree.2066 However, use with care: the final stash application after a2067 successful rebase might result in non-trivial conflicts.2068 Defaults to false.20692070receive.autogc::2071 By default, git-receive-pack will run "git-gc --auto" after2072 receiving data from git-push and updating refs. You can stop2073 it by setting this variable to false.20742075receive.certnonceseed::2076 By setting this variable to a string, `git receive-pack`2077 will accept a `git push --signed` and verifies it by using2078 a "nonce" protected by HMAC using this string as a secret2079 key.20802081receive.certnonceslop::2082 When a `git push --signed` sent a push certificate with a2083 "nonce" that was issued by a receive-pack serving the same2084 repository within this many seconds, export the "nonce"2085 found in the certificate to `GIT_PUSH_CERT_NONCE` to the2086 hooks (instead of what the receive-pack asked the sending2087 side to include). This may allow writing checks in2088 `pre-receive` and `post-receive` a bit easier. Instead of2089 checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable2090 that records by how many seconds the nonce is stale to2091 decide if they want to accept the certificate, they only2092 can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.20932094receive.fsckObjects::2095 If it is set to true, git-receive-pack will check all received2096 objects. It will abort in the case of a malformed object or a2097 broken link. The result of an abort are only dangling objects.2098 Defaults to false. If not set, the value of `transfer.fsckObjects`2099 is used instead.21002101receive.unpackLimit::2102 If the number of objects received in a push is below this2103 limit then the objects will be unpacked into loose object2104 files. However if the number of received objects equals or2105 exceeds this limit then the received pack will be stored as2106 a pack, after adding any missing delta bases. Storing the2107 pack from a push can make the push operation complete faster,2108 especially on slow filesystems. If not set, the value of2109 `transfer.unpackLimit` is used instead.21102111receive.denyDeletes::2112 If set to true, git-receive-pack will deny a ref update that deletes2113 the ref. Use this to prevent such a ref deletion via a push.21142115receive.denyDeleteCurrent::2116 If set to true, git-receive-pack will deny a ref update that2117 deletes the currently checked out branch of a non-bare repository.21182119receive.denyCurrentBranch::2120 If set to true or "refuse", git-receive-pack will deny a ref update2121 to the currently checked out branch of a non-bare repository.2122 Such a push is potentially dangerous because it brings the HEAD2123 out of sync with the index and working tree. If set to "warn",2124 print a warning of such a push to stderr, but allow the push to2125 proceed. If set to false or "ignore", allow such pushes with no2126 message. Defaults to "refuse".21272128receive.denyNonFastForwards::2129 If set to true, git-receive-pack will deny a ref update which is2130 not a fast-forward. Use this to prevent such an update via a push,2131 even if that push is forced. This configuration variable is2132 set when initializing a shared repository.21332134receive.hiderefs::2135 String(s) `receive-pack` uses to decide which refs to omit2136 from its initial advertisement. Use more than one2137 definitions to specify multiple prefix strings. A ref that2138 are under the hierarchies listed on the value of this2139 variable is excluded, and is hidden when responding to `git2140 push`, and an attempt to update or delete a hidden ref by2141 `git push` is rejected.21422143receive.updateserverinfo::2144 If set to true, git-receive-pack will run git-update-server-info2145 after receiving data from git-push and updating refs.21462147receive.shallowupdate::2148 If set to true, .git/shallow can be updated when new refs2149 require new shallow roots. Otherwise those refs are rejected.21502151remote.pushdefault::2152 The remote to push to by default. Overrides2153 `branch.<name>.remote` for all branches, and is overridden by2154 `branch.<name>.pushremote` for specific branches.21552156remote.<name>.url::2157 The URL of a remote repository. See linkgit:git-fetch[1] or2158 linkgit:git-push[1].21592160remote.<name>.pushurl::2161 The push URL of a remote repository. See linkgit:git-push[1].21622163remote.<name>.proxy::2164 For remotes that require curl (http, https and ftp), the URL to2165 the proxy to use for that remote. Set to the empty string to2166 disable proxying for that remote.21672168remote.<name>.fetch::2169 The default set of "refspec" for linkgit:git-fetch[1]. See2170 linkgit:git-fetch[1].21712172remote.<name>.push::2173 The default set of "refspec" for linkgit:git-push[1]. See2174 linkgit:git-push[1].21752176remote.<name>.mirror::2177 If true, pushing to this remote will automatically behave2178 as if the `--mirror` option was given on the command line.21792180remote.<name>.skipDefaultUpdate::2181 If true, this remote will be skipped by default when updating2182 using linkgit:git-fetch[1] or the `update` subcommand of2183 linkgit:git-remote[1].21842185remote.<name>.skipFetchAll::2186 If true, this remote will be skipped by default when updating2187 using linkgit:git-fetch[1] or the `update` subcommand of2188 linkgit:git-remote[1].21892190remote.<name>.receivepack::2191 The default program to execute on the remote side when pushing. See2192 option \--receive-pack of linkgit:git-push[1].21932194remote.<name>.uploadpack::2195 The default program to execute on the remote side when fetching. See2196 option \--upload-pack of linkgit:git-fetch-pack[1].21972198remote.<name>.tagopt::2199 Setting this value to \--no-tags disables automatic tag following when2200 fetching from remote <name>. Setting it to \--tags will fetch every2201 tag from remote <name>, even if they are not reachable from remote2202 branch heads. Passing these flags directly to linkgit:git-fetch[1] can2203 override this setting. See options \--tags and \--no-tags of2204 linkgit:git-fetch[1].22052206remote.<name>.vcs::2207 Setting this to a value <vcs> will cause Git to interact with2208 the remote with the git-remote-<vcs> helper.22092210remote.<name>.prune::2211 When set to true, fetching from this remote by default will also2212 remove any remote-tracking references that no longer exist on the2213 remote (as if the `--prune` option was given on the command line).2214 Overrides `fetch.prune` settings, if any.22152216remotes.<group>::2217 The list of remotes which are fetched by "git remote update2218 <group>". See linkgit:git-remote[1].22192220repack.usedeltabaseoffset::2221 By default, linkgit:git-repack[1] creates packs that use2222 delta-base offset. If you need to share your repository with2223 Git older than version 1.4.4, either directly or via a dumb2224 protocol such as http, then you need to set this option to2225 "false" and repack. Access from old Git versions over the2226 native protocol are unaffected by this option.22272228repack.packKeptObjects::2229 If set to true, makes `git repack` act as if2230 `--pack-kept-objects` was passed. See linkgit:git-repack[1] for2231 details. Defaults to `false` normally, but `true` if a bitmap2232 index is being written (either via `--write-bitmap-index` or2233 `repack.writeBitmaps`).22342235repack.writeBitmaps::2236 When true, git will write a bitmap index when packing all2237 objects to disk (e.g., when `git repack -a` is run). This2238 index can speed up the "counting objects" phase of subsequent2239 packs created for clones and fetches, at the cost of some disk2240 space and extra time spent on the initial repack. Defaults to2241 false.22422243rerere.autoupdate::2244 When set to true, `git-rerere` updates the index with the2245 resulting contents after it cleanly resolves conflicts using2246 previously recorded resolution. Defaults to false.22472248rerere.enabled::2249 Activate recording of resolved conflicts, so that identical2250 conflict hunks can be resolved automatically, should they be2251 encountered again. By default, linkgit:git-rerere[1] is2252 enabled if there is an `rr-cache` directory under the2253 `$GIT_DIR`, e.g. if "rerere" was previously used in the2254 repository.22552256sendemail.identity::2257 A configuration identity. When given, causes values in the2258 'sendemail.<identity>' subsection to take precedence over2259 values in the 'sendemail' section. The default identity is2260 the value of 'sendemail.identity'.22612262sendemail.smtpencryption::2263 See linkgit:git-send-email[1] for description. Note that this2264 setting is not subject to the 'identity' mechanism.22652266sendemail.smtpssl::2267 Deprecated alias for 'sendemail.smtpencryption = ssl'.22682269sendemail.smtpsslcertpath::2270 Path to ca-certificates (either a directory or a single file).2271 Set it to an empty string to disable certificate verification.22722273sendemail.<identity>.*::2274 Identity-specific versions of the 'sendemail.*' parameters2275 found below, taking precedence over those when the this2276 identity is selected, through command-line or2277 'sendemail.identity'.22782279sendemail.aliasesfile::2280sendemail.aliasfiletype::2281sendemail.annotate::2282sendemail.bcc::2283sendemail.cc::2284sendemail.cccmd::2285sendemail.chainreplyto::2286sendemail.confirm::2287sendemail.envelopesender::2288sendemail.from::2289sendemail.multiedit::2290sendemail.signedoffbycc::2291sendemail.smtppass::2292sendemail.suppresscc::2293sendemail.suppressfrom::2294sendemail.to::2295sendemail.smtpdomain::2296sendemail.smtpserver::2297sendemail.smtpserverport::2298sendemail.smtpserveroption::2299sendemail.smtpuser::2300sendemail.thread::2301sendemail.validate::2302 See linkgit:git-send-email[1] for description.23032304sendemail.signedoffcc::2305 Deprecated alias for 'sendemail.signedoffbycc'.23062307showbranch.default::2308 The default set of branches for linkgit:git-show-branch[1].2309 See linkgit:git-show-branch[1].23102311status.relativePaths::2312 By default, linkgit:git-status[1] shows paths relative to the2313 current directory. Setting this variable to `false` shows paths2314 relative to the repository root (this was the default for Git2315 prior to v1.5.4).23162317status.short::2318 Set to true to enable --short by default in linkgit:git-status[1].2319 The option --no-short takes precedence over this variable.23202321status.branch::2322 Set to true to enable --branch by default in linkgit:git-status[1].2323 The option --no-branch takes precedence over this variable.23242325status.displayCommentPrefix::2326 If set to true, linkgit:git-status[1] will insert a comment2327 prefix before each output line (starting with2328 `core.commentChar`, i.e. `#` by default). This was the2329 behavior of linkgit:git-status[1] in Git 1.8.4 and previous.2330 Defaults to false.23312332status.showUntrackedFiles::2333 By default, linkgit:git-status[1] and linkgit:git-commit[1] show2334 files which are not currently tracked by Git. Directories which2335 contain only untracked files, are shown with the directory name2336 only. Showing untracked files means that Git needs to lstat() all2337 all the files in the whole repository, which might be slow on some2338 systems. So, this variable controls how the commands displays2339 the untracked files. Possible values are:2340+2341--2342* `no` - Show no untracked files.2343* `normal` - Show untracked files and directories.2344* `all` - Show also individual files in untracked directories.2345--2346+2347If this variable is not specified, it defaults to 'normal'.2348This variable can be overridden with the -u|--untracked-files option2349of linkgit:git-status[1] and linkgit:git-commit[1].23502351status.submodulesummary::2352 Defaults to false.2353 If this is set to a non zero number or true (identical to -1 or an2354 unlimited number), the submodule summary will be enabled and a2355 summary of commits for modified submodules will be shown (see2356 --summary-limit option of linkgit:git-submodule[1]). Please note2357 that the summary output command will be suppressed for all2358 submodules when `diff.ignoreSubmodules` is set to 'all' or only2359 for those submodules where `submodule.<name>.ignore=all`. The only2360 exception to that rule is that status and commit will show staged2361 submodule changes. To2362 also view the summary for ignored submodules you can either use2363 the --ignore-submodules=dirty command-line option or the 'git2364 submodule summary' command, which shows a similar output but does2365 not honor these settings.23662367submodule.<name>.path::2368submodule.<name>.url::2369submodule.<name>.update::2370 The path within this project, URL, and the updating strategy2371 for a submodule. These variables are initially populated2372 by 'git submodule init'; edit them to override the2373 URL and other values found in the `.gitmodules` file. See2374 linkgit:git-submodule[1] and linkgit:gitmodules[5] for details.23752376submodule.<name>.branch::2377 The remote branch name for a submodule, used by `git submodule2378 update --remote`. Set this option to override the value found in2379 the `.gitmodules` file. See linkgit:git-submodule[1] and2380 linkgit:gitmodules[5] for details.23812382submodule.<name>.fetchRecurseSubmodules::2383 This option can be used to control recursive fetching of this2384 submodule. It can be overridden by using the --[no-]recurse-submodules2385 command-line option to "git fetch" and "git pull".2386 This setting will override that from in the linkgit:gitmodules[5]2387 file.23882389submodule.<name>.ignore::2390 Defines under what circumstances "git status" and the diff family show2391 a submodule as modified. When set to "all", it will never be considered2392 modified (but it will nonetheless show up in the output of status and2393 commit when it has been staged), "dirty" will ignore all changes2394 to the submodules work tree and2395 takes only differences between the HEAD of the submodule and the commit2396 recorded in the superproject into account. "untracked" will additionally2397 let submodules with modified tracked files in their work tree show up.2398 Using "none" (the default when this option is not set) also shows2399 submodules that have untracked files in their work tree as changed.2400 This setting overrides any setting made in .gitmodules for this submodule,2401 both settings can be overridden on the command line by using the2402 "--ignore-submodules" option. The 'git submodule' commands are not2403 affected by this setting.24042405tag.sort::2406 This variable controls the sort ordering of tags when displayed by2407 linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the2408 value of this variable will be used as the default.24092410tar.umask::2411 This variable can be used to restrict the permission bits of2412 tar archive entries. The default is 0002, which turns off the2413 world write bit. The special value "user" indicates that the2414 archiving user's umask will be used instead. See umask(2) and2415 linkgit:git-archive[1].24162417transfer.fsckObjects::2418 When `fetch.fsckObjects` or `receive.fsckObjects` are2419 not set, the value of this variable is used instead.2420 Defaults to false.24212422transfer.hiderefs::2423 This variable can be used to set both `receive.hiderefs`2424 and `uploadpack.hiderefs` at the same time to the same2425 values. See entries for these other variables.24262427transfer.unpackLimit::2428 When `fetch.unpackLimit` or `receive.unpackLimit` are2429 not set, the value of this variable is used instead.2430 The default value is 100.24312432uploadarchive.allowUnreachable::2433 If true, allow clients to use `git archive --remote` to request2434 any tree, whether reachable from the ref tips or not. See the2435 discussion in the `SECURITY` section of2436 linkgit:git-upload-archive[1] for more details. Defaults to2437 `false`.24382439uploadpack.hiderefs::2440 String(s) `upload-pack` uses to decide which refs to omit2441 from its initial advertisement. Use more than one2442 definitions to specify multiple prefix strings. A ref that2443 are under the hierarchies listed on the value of this2444 variable is excluded, and is hidden from `git ls-remote`,2445 `git fetch`, etc. An attempt to fetch a hidden ref by `git2446 fetch` will fail. See also `uploadpack.allowtipsha1inwant`.24472448uploadpack.allowtipsha1inwant::2449 When `uploadpack.hiderefs` is in effect, allow `upload-pack`2450 to accept a fetch request that asks for an object at the tip2451 of a hidden ref (by default, such a request is rejected).2452 see also `uploadpack.hiderefs`.24532454uploadpack.keepalive::2455 When `upload-pack` has started `pack-objects`, there may be a2456 quiet period while `pack-objects` prepares the pack. Normally2457 it would output progress information, but if `--quiet` was used2458 for the fetch, `pack-objects` will output nothing at all until2459 the pack data begins. Some clients and networks may consider2460 the server to be hung and give up. Setting this option instructs2461 `upload-pack` to send an empty keepalive packet every2462 `uploadpack.keepalive` seconds. Setting this option to 02463 disables keepalive packets entirely. The default is 5 seconds.24642465url.<base>.insteadOf::2466 Any URL that starts with this value will be rewritten to2467 start, instead, with <base>. In cases where some site serves a2468 large number of repositories, and serves them with multiple2469 access methods, and some users need to use different access2470 methods, this feature allows people to specify any of the2471 equivalent URLs and have Git automatically rewrite the URL to2472 the best alternative for the particular user, even for a2473 never-before-seen repository on the site. When more than one2474 insteadOf strings match a given URL, the longest match is used.24752476url.<base>.pushInsteadOf::2477 Any URL that starts with this value will not be pushed to;2478 instead, it will be rewritten to start with <base>, and the2479 resulting URL will be pushed to. In cases where some site serves2480 a large number of repositories, and serves them with multiple2481 access methods, some of which do not allow push, this feature2482 allows people to specify a pull-only URL and have Git2483 automatically use an appropriate URL to push, even for a2484 never-before-seen repository on the site. When more than one2485 pushInsteadOf strings match a given URL, the longest match is2486 used. If a remote has an explicit pushurl, Git will ignore this2487 setting for that remote.24882489user.email::2490 Your email address to be recorded in any newly created commits.2491 Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and2492 'EMAIL' environment variables. See linkgit:git-commit-tree[1].24932494user.name::2495 Your full name to be recorded in any newly created commits.2496 Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'2497 environment variables. See linkgit:git-commit-tree[1].24982499user.signingkey::2500 If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the2501 key you want it to automatically when creating a signed tag or2502 commit, you can override the default selection with this variable.2503 This option is passed unchanged to gpg's --local-user parameter,2504 so you may specify a key using any method that gpg supports.25052506web.browser::2507 Specify a web browser that may be used by some commands.2508 Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]2509 may use it.