Documentation / config.txton commit rev-parse --parseopt: allow [*=?!] in argument hints (2d893df)
   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; we say then that the variable is
  18multivalued.
  19
  20Syntax
  21~~~~~~
  22
  23The syntax is fairly flexible and permissive; whitespaces are mostly
  24ignored.  The '#' and ';' characters begin comments to the end of line,
  25blank lines are ignored.
  26
  27The file consists of sections and variables.  A section begins with
  28the name of the section in square brackets and continues until the next
  29section begins.  Section names are case-insensitive.  Only alphanumeric
  30characters, `-` and `.` are allowed in section names.  Each variable
  31must belong to some section, which means that there must be a section
  32header before the first setting of a variable.
  33
  34Sections can be further divided into subsections.  To begin a subsection
  35put its name in double quotes, separated by space from the section name,
  36in the section header, like in the example below:
  37
  38--------
  39        [section "subsection"]
  40
  41--------
  42
  43Subsection names are case sensitive and can contain any characters except
  44newline (doublequote `"` and backslash can be included by escaping them
  45as `\"` and `\\`, respectively).  Section headers cannot span multiple
  46lines.  Variables may belong directly to a section or to a given subsection.
  47You can have `[section]` if you have `[section "subsection"]`, but you
  48don't need to.
  49
  50There is also a deprecated `[section.subsection]` syntax. With this
  51syntax, the subsection name is converted to lower-case and is also
  52compared case sensitively. These subsection names follow the same
  53restrictions as section names.
  54
  55All the other lines (and the remainder of the line after the section
  56header) are recognized as setting variables, in the form
  57'name = value' (or just 'name', which is a short-hand to say that
  58the variable is the boolean "true").
  59The variable names are case-insensitive, allow only alphanumeric characters
  60and `-`, and must start with an alphabetic character.
  61
  62A line that defines a value can be continued to the next line by
  63ending it with a `\`; the backquote and the end-of-line are
  64stripped.  Leading whitespaces after 'name =', the remainder of the
  65line after the first comment character '#' or ';', and trailing
  66whitespaces of the line are discarded unless they are enclosed in
  67double quotes.  Internal whitespaces within the value are retained
  68verbatim.
  69
  70Inside double quotes, double quote `"` and backslash `\` characters
  71must be escaped: use `\"` for `"` and `\\` for `\`.
  72
  73The following escape sequences (beside `\"` and `\\`) are recognized:
  74`\n` for newline character (NL), `\t` for horizontal tabulation (HT, TAB)
  75and `\b` for backspace (BS).  Other char escape sequences (including octal
  76escape sequences) are invalid.
  77
  78
  79Includes
  80~~~~~~~~
  81
  82You can include one config file from another by setting the special
  83`include.path` variable to the name of the file to be included. The
  84included file is expanded immediately, as if its contents had been
  85found at the location of the include directive. If the value of the
  86`include.path` variable is a relative path, the path is considered to be
  87relative to the configuration file in which the include directive was
  88found. The value of `include.path` is subject to tilde expansion: `~/`
  89is expanded to the value of `$HOME`, and `~user/` to the specified
  90user's home directory. See below for examples.
  91
  92Example
  93~~~~~~~
  94
  95        # Core variables
  96        [core]
  97                ; Don't trust file modes
  98                filemode = false
  99
 100        # Our diff algorithm
 101        [diff]
 102                external = /usr/local/bin/diff-wrapper
 103                renames = true
 104
 105        [branch "devel"]
 106                remote = origin
 107                merge = refs/heads/devel
 108
 109        # Proxy settings
 110        [core]
 111                gitProxy="ssh" for "kernel.org"
 112                gitProxy=default-proxy ; for the rest
 113
 114        [include]
 115                path = /path/to/foo.inc ; include by absolute path
 116                path = foo ; expand "foo" relative to the current file
 117                path = ~/foo ; expand "foo" in your $HOME directory
 118
 119
 120Values
 121~~~~~~
 122
 123Values of many variables are treated as a simple string, but there
 124are variables that take values of specific types and there are rules
 125as to how to spell them.
 126
 127boolean::
 128
 129       When a variable is said to take a boolean value, many
 130       synonyms are accepted for 'true' and 'false'; these are all
 131       case-insensitive.
 132
 133       true;; Boolean true can be spelled as `yes`, `on`, `true`,
 134                or `1`.  Also, a variable defined without `= <value>`
 135                is taken as true.
 136
 137       false;; Boolean false can be spelled as `no`, `off`,
 138                `false`, or `0`.
 139+
 140When converting value to the canonical form using '--bool' type
 141specifier; 'git config' will ensure that the output is "true" or
 142"false" (spelled in lowercase).
 143
 144integer::
 145       The value for many variables that specify various sizes can
 146       be suffixed with `k`, `M`,... to mean "scale the number by
 147       1024", "by 1024x1024", etc.
 148
 149color::
 150       The value for a variables that takes a color is a list of
 151       colors (at most two) and attributes (at most one), separated
 152       by spaces.  The colors accepted are `normal`, `black`,
 153       `red`, `green`, `yellow`, `blue`, `magenta`, `cyan` and
 154       `white`; the attributes are `bold`, `dim`, `ul`, `blink` and
 155       `reverse`.  The first color given is the foreground; the
 156       second is the background.  The position of the attribute, if
 157       any, doesn't matter. Attributes may be turned off specifically
 158       by prefixing them with `no` (e.g., `noreverse`, `noul`, etc).
 159+
 160Colors (foreground and background) may also be given as numbers between
 1610 and 255; these use ANSI 256-color mode (but note that not all
 162terminals may support this).  If your terminal supports it, you may also
 163specify 24-bit RGB values as hex, like `#ff0ab3`.
 164+
 165The attributes are meant to be reset at the beginning of each item
 166in the colored output, so setting color.decorate.branch to `black`
 167will paint that branch name in a plain `black`, even if the previous
 168thing on the same output line (e.g. opening parenthesis before the
 169list of branch names in `log --decorate` output) is set to be
 170painted with `bold` or some other attribute.
 171
 172
 173Variables
 174~~~~~~~~~
 175
 176Note that this list is non-comprehensive and not necessarily complete.
 177For command-specific variables, you will find a more detailed description
 178in the appropriate manual page.
 179
 180Other git-related tools may and do use their own variables.  When
 181inventing new variables for use in your own tool, make sure their
 182names do not conflict with those that are used by Git itself and
 183other popular tools, and describe them in your documentation.
 184
 185
 186advice.*::
 187        These variables control various optional help messages designed to
 188        aid new users. All 'advice.*' variables default to 'true', and you
 189        can tell Git that you do not need help by setting these to 'false':
 190+
 191--
 192        pushUpdateRejected::
 193                Set this variable to 'false' if you want to disable
 194                'pushNonFFCurrent',
 195                'pushNonFFMatching', 'pushAlreadyExists',
 196                'pushFetchFirst', and 'pushNeedsForce'
 197                simultaneously.
 198        pushNonFFCurrent::
 199                Advice shown when linkgit:git-push[1] fails due to a
 200                non-fast-forward update to the current branch.
 201        pushNonFFMatching::
 202                Advice shown when you ran linkgit:git-push[1] and pushed
 203                'matching refs' explicitly (i.e. you used ':', or
 204                specified a refspec that isn't your current branch) and
 205                it resulted in a non-fast-forward error.
 206        pushAlreadyExists::
 207                Shown when linkgit:git-push[1] rejects an update that
 208                does not qualify for fast-forwarding (e.g., a tag.)
 209        pushFetchFirst::
 210                Shown when linkgit:git-push[1] rejects an update that
 211                tries to overwrite a remote ref that points at an
 212                object we do not have.
 213        pushNeedsForce::
 214                Shown when linkgit:git-push[1] rejects an update that
 215                tries to overwrite a remote ref that points at an
 216                object that is not a commit-ish, or make the remote
 217                ref point at an object that is not a commit-ish.
 218        statusHints::
 219                Show directions on how to proceed from the current
 220                state in the output of linkgit:git-status[1], in
 221                the template shown when writing commit messages in
 222                linkgit:git-commit[1], and in the help message shown
 223                by linkgit:git-checkout[1] when switching branch.
 224        statusUoption::
 225                Advise to consider using the `-u` option to linkgit:git-status[1]
 226                when the command takes more than 2 seconds to enumerate untracked
 227                files.
 228        commitBeforeMerge::
 229                Advice shown when linkgit:git-merge[1] refuses to
 230                merge to avoid overwriting local changes.
 231        resolveConflict::
 232                Advice shown by various commands when conflicts
 233                prevent the operation from being performed.
 234        implicitIdentity::
 235                Advice on how to set your identity configuration when
 236                your information is guessed from the system username and
 237                domain name.
 238        detachedHead::
 239                Advice shown when you used linkgit:git-checkout[1] to
 240                move to the detach HEAD state, to instruct how to create
 241                a local branch after the fact.
 242        amWorkDir::
 243                Advice that shows the location of the patch file when
 244                linkgit:git-am[1] fails to apply it.
 245        rmHints::
 246                In case of failure in the output of linkgit:git-rm[1],
 247                show directions on how to proceed from the current state.
 248--
 249
 250core.fileMode::
 251        Tells Git if the executable bit of files in the working tree
 252        is to be honored.
 253+
 254Some filesystems lose the executable bit when a file that is
 255marked as executable is checked out, or checks out an
 256non-executable file with executable bit on.
 257linkgit:git-clone[1] or linkgit:git-init[1] probe the filesystem
 258to see if it handles the executable bit correctly
 259and this variable is automatically set as necessary.
 260+
 261A repository, however, may be on a filesystem that handles
 262the filemode correctly, and this variable is set to 'true'
 263when created, but later may be made accessible from another
 264environment that loses the filemode (e.g. exporting ext4 via
 265CIFS mount, visiting a Cygwin created repository with
 266Git for Windows or Eclipse).
 267In such a case it may be necessary to set this variable to 'false'.
 268See linkgit:git-update-index[1].
 269+
 270The default is true (when core.filemode is not specified in the config file).
 271
 272core.ignoreCase::
 273        If true, this option enables various workarounds to enable
 274        Git to work better on filesystems that are not case sensitive,
 275        like FAT. For example, if a directory listing finds
 276        "makefile" when Git expects "Makefile", Git will assume
 277        it is really the same file, and continue to remember it as
 278        "Makefile".
 279+
 280The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]
 281will probe and set core.ignoreCase true if appropriate when the repository
 282is created.
 283
 284core.precomposeUnicode::
 285        This option is only used by Mac OS implementation of Git.
 286        When core.precomposeUnicode=true, Git reverts the unicode decomposition
 287        of filenames done by Mac OS. This is useful when sharing a repository
 288        between Mac OS and Linux or Windows.
 289        (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).
 290        When false, file names are handled fully transparent by Git,
 291        which is backward compatible with older versions of Git.
 292
 293core.protectHFS::
 294        If set to true, do not allow checkout of paths that would
 295        be considered equivalent to `.git` on an HFS+ filesystem.
 296        Defaults to `true` on Mac OS, and `false` elsewhere.
 297
 298core.protectNTFS::
 299        If set to true, do not allow checkout of paths that would
 300        cause problems with the NTFS filesystem, e.g. conflict with
 301        8.3 "short" names.
 302        Defaults to `true` on Windows, and `false` elsewhere.
 303
 304core.trustctime::
 305        If false, the ctime differences between the index and the
 306        working tree are ignored; useful when the inode change time
 307        is regularly modified by something outside Git (file system
 308        crawlers and some backup systems).
 309        See linkgit:git-update-index[1]. True by default.
 310
 311core.checkStat::
 312        Determines which stat fields to match between the index
 313        and work tree. The user can set this to 'default' or
 314        'minimal'. Default (or explicitly 'default'), is to check
 315        all fields, including the sub-second part of mtime and ctime.
 316
 317core.quotePath::
 318        The commands that output paths (e.g. 'ls-files',
 319        'diff'), when not given the `-z` option, will quote
 320        "unusual" characters in the pathname by enclosing the
 321        pathname in a double-quote pair and with backslashes the
 322        same way strings in C source code are quoted.  If this
 323        variable is set to false, the bytes higher than 0x80 are
 324        not quoted but output as verbatim.  Note that double
 325        quote, backslash and control characters are always
 326        quoted without `-z` regardless of the setting of this
 327        variable.
 328
 329core.eol::
 330        Sets the line ending type to use in the working directory for
 331        files that have the `text` property set.  Alternatives are
 332        'lf', 'crlf' and 'native', which uses the platform's native
 333        line ending.  The default value is `native`.  See
 334        linkgit:gitattributes[5] for more information on end-of-line
 335        conversion.
 336
 337core.safecrlf::
 338        If true, makes Git check if converting `CRLF` is reversible when
 339        end-of-line conversion is active.  Git will verify if a command
 340        modifies a file in the work tree either directly or indirectly.
 341        For example, committing a file followed by checking out the
 342        same file should yield the original file in the work tree.  If
 343        this is not the case for the current setting of
 344        `core.autocrlf`, Git will reject the file.  The variable can
 345        be set to "warn", in which case Git will only warn about an
 346        irreversible conversion but continue the operation.
 347+
 348CRLF conversion bears a slight chance of corrupting data.
 349When it is enabled, Git will convert CRLF to LF during commit and LF to
 350CRLF during checkout.  A file that contains a mixture of LF and
 351CRLF before the commit cannot be recreated by Git.  For text
 352files this is the right thing to do: it corrects line endings
 353such that we have only LF line endings in the repository.
 354But for binary files that are accidentally classified as text the
 355conversion can corrupt data.
 356+
 357If you recognize such corruption early you can easily fix it by
 358setting the conversion type explicitly in .gitattributes.  Right
 359after committing you still have the original file in your work
 360tree and this file is not yet corrupted.  You can explicitly tell
 361Git that this file is binary and Git will handle the file
 362appropriately.
 363+
 364Unfortunately, the desired effect of cleaning up text files with
 365mixed line endings and the undesired effect of corrupting binary
 366files cannot be distinguished.  In both cases CRLFs are removed
 367in an irreversible way.  For text files this is the right thing
 368to do because CRLFs are line endings, while for binary files
 369converting CRLFs corrupts data.
 370+
 371Note, this safety check does not mean that a checkout will generate a
 372file identical to the original file for a different setting of
 373`core.eol` and `core.autocrlf`, but only for the current one.  For
 374example, a text file with `LF` would be accepted with `core.eol=lf`
 375and could later be checked out with `core.eol=crlf`, in which case the
 376resulting file would contain `CRLF`, although the original file
 377contained `LF`.  However, in both work trees the line endings would be
 378consistent, that is either all `LF` or all `CRLF`, but never mixed.  A
 379file with mixed line endings would be reported by the `core.safecrlf`
 380mechanism.
 381
 382core.autocrlf::
 383        Setting this variable to "true" is almost the same as setting
 384        the `text` attribute to "auto" on all files except that text
 385        files are not guaranteed to be normalized: files that contain
 386        `CRLF` in the repository will not be touched.  Use this
 387        setting if you want to have `CRLF` line endings in your
 388        working directory even though the repository does not have
 389        normalized line endings.  This variable can be set to 'input',
 390        in which case no output conversion is performed.
 391
 392core.symlinks::
 393        If false, symbolic links are checked out as small plain files that
 394        contain the link text. linkgit:git-update-index[1] and
 395        linkgit:git-add[1] will not change the recorded type to regular
 396        file. Useful on filesystems like FAT that do not support
 397        symbolic links.
 398+
 399The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]
 400will probe and set core.symlinks false if appropriate when the repository
 401is created.
 402
 403core.gitProxy::
 404        A "proxy command" to execute (as 'command host port') instead
 405        of establishing direct connection to the remote server when
 406        using the Git protocol for fetching. If the variable value is
 407        in the "COMMAND for DOMAIN" format, the command is applied only
 408        on hostnames ending with the specified domain string. This variable
 409        may be set multiple times and is matched in the given order;
 410        the first match wins.
 411+
 412Can be overridden by the 'GIT_PROXY_COMMAND' environment variable
 413(which always applies universally, without the special "for"
 414handling).
 415+
 416The special string `none` can be used as the proxy command to
 417specify that no proxy be used for a given domain pattern.
 418This is useful for excluding servers inside a firewall from
 419proxy use, while defaulting to a common proxy for external domains.
 420
 421core.ignoreStat::
 422        If true, Git will avoid using lstat() calls to detect if files have
 423        changed by setting the "assume-unchanged" bit for those tracked files
 424        which it has updated identically in both the index and working tree.
 425+
 426When files are modified outside of Git, the user will need to stage
 427the modified files explicitly (e.g. see 'Examples' section in
 428linkgit:git-update-index[1]).
 429Git will not normally detect changes to those files.
 430+
 431This is useful on systems where lstat() calls are very slow, such as
 432CIFS/Microsoft Windows.
 433+
 434False by default.
 435
 436core.preferSymlinkRefs::
 437        Instead of the default "symref" format for HEAD
 438        and other symbolic reference files, use symbolic links.
 439        This is sometimes needed to work with old scripts that
 440        expect HEAD to be a symbolic link.
 441
 442core.bare::
 443        If true this repository is assumed to be 'bare' and has no
 444        working directory associated with it.  If this is the case a
 445        number of commands that require a working directory will be
 446        disabled, such as linkgit:git-add[1] or linkgit:git-merge[1].
 447+
 448This setting is automatically guessed by linkgit:git-clone[1] or
 449linkgit:git-init[1] when the repository was created.  By default a
 450repository that ends in "/.git" is assumed to be not bare (bare =
 451false), while all other repositories are assumed to be bare (bare
 452= true).
 453
 454core.worktree::
 455        Set the path to the root of the working tree.
 456        If GIT_COMMON_DIR environment variable is set, core.worktree
 457        is ignored and not used for determining the root of working tree.
 458        This can be overridden by the GIT_WORK_TREE environment
 459        variable and the '--work-tree' command-line option.
 460        The value can be an absolute path or relative to the path to
 461        the .git directory, which is either specified by --git-dir
 462        or GIT_DIR, or automatically discovered.
 463        If --git-dir or GIT_DIR is specified but none of
 464        --work-tree, GIT_WORK_TREE and core.worktree is specified,
 465        the current working directory is regarded as the top level
 466        of your working tree.
 467+
 468Note that this variable is honored even when set in a configuration
 469file in a ".git" subdirectory of a directory and its value differs
 470from the latter directory (e.g. "/path/to/.git/config" has
 471core.worktree set to "/different/path"), which is most likely a
 472misconfiguration.  Running Git commands in the "/path/to" directory will
 473still use "/different/path" as the root of the work tree and can cause
 474confusion unless you know what you are doing (e.g. you are creating a
 475read-only snapshot of the same index to a location different from the
 476repository's usual working tree).
 477
 478core.logAllRefUpdates::
 479        Enable the reflog. Updates to a ref <ref> is logged to the file
 480        "$GIT_DIR/logs/<ref>", by appending the new and old
 481        SHA-1, the date/time and the reason of the update, but
 482        only when the file exists.  If this configuration
 483        variable is set to true, missing "$GIT_DIR/logs/<ref>"
 484        file is automatically created for branch heads (i.e. under
 485        refs/heads/), remote refs (i.e. under refs/remotes/),
 486        note refs (i.e. under refs/notes/), and the symbolic ref HEAD.
 487+
 488This information can be used to determine what commit
 489was the tip of a branch "2 days ago".
 490+
 491This value is true by default in a repository that has
 492a working directory associated with it, and false by
 493default in a bare repository.
 494
 495core.repositoryFormatVersion::
 496        Internal variable identifying the repository format and layout
 497        version.
 498
 499core.sharedRepository::
 500        When 'group' (or 'true'), the repository is made shareable between
 501        several users in a group (making sure all the files and objects are
 502        group-writable). When 'all' (or 'world' or 'everybody'), the
 503        repository will be readable by all users, additionally to being
 504        group-shareable. When 'umask' (or 'false'), Git will use permissions
 505        reported by umask(2). When '0xxx', where '0xxx' is an octal number,
 506        files in the repository will have this mode value. '0xxx' will override
 507        user's umask value (whereas the other options will only override
 508        requested parts of the user's umask value). Examples: '0660' will make
 509        the repo read/write-able for the owner and group, but inaccessible to
 510        others (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a
 511        repository that is group-readable but not group-writable.
 512        See linkgit:git-init[1]. False by default.
 513
 514core.warnAmbiguousRefs::
 515        If true, Git will warn you if the ref name you passed it is ambiguous
 516        and might match multiple refs in the repository. True by default.
 517
 518core.compression::
 519        An integer -1..9, indicating a default compression level.
 520        -1 is the zlib default. 0 means no compression,
 521        and 1..9 are various speed/size tradeoffs, 9 being slowest.
 522        If set, this provides a default to other compression variables,
 523        such as 'core.looseCompression' and 'pack.compression'.
 524
 525core.looseCompression::
 526        An integer -1..9, indicating the compression level for objects that
 527        are not in a pack file. -1 is the zlib default. 0 means no
 528        compression, and 1..9 are various speed/size tradeoffs, 9 being
 529        slowest.  If not set,  defaults to core.compression.  If that is
 530        not set,  defaults to 1 (best speed).
 531
 532core.packedGitWindowSize::
 533        Number of bytes of a pack file to map into memory in a
 534        single mapping operation.  Larger window sizes may allow
 535        your system to process a smaller number of large pack files
 536        more quickly.  Smaller window sizes will negatively affect
 537        performance due to increased calls to the operating system's
 538        memory manager, but may improve performance when accessing
 539        a large number of large pack files.
 540+
 541Default is 1 MiB if NO_MMAP was set at compile time, otherwise 32
 542MiB on 32 bit platforms and 1 GiB on 64 bit platforms.  This should
 543be reasonable for all users/operating systems.  You probably do
 544not need to adjust this value.
 545+
 546Common unit suffixes of 'k', 'm', or 'g' are supported.
 547
 548core.packedGitLimit::
 549        Maximum number of bytes to map simultaneously into memory
 550        from pack files.  If Git needs to access more than this many
 551        bytes at once to complete an operation it will unmap existing
 552        regions to reclaim virtual address space within the process.
 553+
 554Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
 555This should be reasonable for all users/operating systems, except on
 556the largest projects.  You probably do not need to adjust this value.
 557+
 558Common unit suffixes of 'k', 'm', or 'g' are supported.
 559
 560core.deltaBaseCacheLimit::
 561        Maximum number of bytes to reserve for caching base objects
 562        that may be referenced by multiple deltified objects.  By storing the
 563        entire decompressed base objects in a cache Git is able
 564        to avoid unpacking and decompressing frequently used base
 565        objects multiple times.
 566+
 567Default is 96 MiB on all platforms.  This should be reasonable
 568for all users/operating systems, except on the largest projects.
 569You probably do not need to adjust this value.
 570+
 571Common unit suffixes of 'k', 'm', or 'g' are supported.
 572
 573core.bigFileThreshold::
 574        Files larger than this size are stored deflated, without
 575        attempting delta compression.  Storing large files without
 576        delta compression avoids excessive memory usage, at the
 577        slight expense of increased disk usage. Additionally files
 578        larger than this size are always treated as binary.
 579+
 580Default is 512 MiB on all platforms.  This should be reasonable
 581for most projects as source code and other text files can still
 582be delta compressed, but larger binary media files won't be.
 583+
 584Common unit suffixes of 'k', 'm', or 'g' are supported.
 585
 586core.excludesFile::
 587        In addition to '.gitignore' (per-directory) and
 588        '.git/info/exclude', Git looks into this file for patterns
 589        of files which are not meant to be tracked.  "`~/`" is expanded
 590        to the value of `$HOME` and "`~user/`" to the specified user's
 591        home directory. Its default value is $XDG_CONFIG_HOME/git/ignore.
 592        If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore
 593        is used instead. See linkgit:gitignore[5].
 594
 595core.askPass::
 596        Some commands (e.g. svn and http interfaces) that interactively
 597        ask for a password can be told to use an external program given
 598        via the value of this variable. Can be overridden by the 'GIT_ASKPASS'
 599        environment variable. If not set, fall back to the value of the
 600        'SSH_ASKPASS' environment variable or, failing that, a simple password
 601        prompt. The external program shall be given a suitable prompt as
 602        command-line argument and write the password on its STDOUT.
 603
 604core.attributesFile::
 605        In addition to '.gitattributes' (per-directory) and
 606        '.git/info/attributes', Git looks into this file for attributes
 607        (see linkgit:gitattributes[5]). Path expansions are made the same
 608        way as for `core.excludesFile`. Its default value is
 609        $XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not
 610        set or empty, $HOME/.config/git/attributes is used instead.
 611
 612core.editor::
 613        Commands such as `commit` and `tag` that lets you edit
 614        messages by launching an editor uses the value of this
 615        variable when it is set, and the environment variable
 616        `GIT_EDITOR` is not set.  See linkgit:git-var[1].
 617
 618core.commentChar::
 619        Commands such as `commit` and `tag` that lets you edit
 620        messages consider a line that begins with this character
 621        commented, and removes them after the editor returns
 622        (default '#').
 623+
 624If set to "auto", `git-commit` would select a character that is not
 625the beginning character of any line in existing commit messages.
 626
 627core.packedRefsTimeout::
 628        The length of time, in milliseconds, to retry when trying to
 629        lock the `packed-refs` file. Value 0 means not to retry at
 630        all; -1 means to try indefinitely. Default is 1000 (i.e.,
 631        retry for 1 second).
 632
 633sequence.editor::
 634        Text editor used by `git rebase -i` for editing the rebase instruction file.
 635        The value is meant to be interpreted by the shell when it is used.
 636        It can be overridden by the `GIT_SEQUENCE_EDITOR` environment variable.
 637        When not configured the default commit message editor is used instead.
 638
 639core.pager::
 640        Text viewer for use by Git commands (e.g., 'less').  The value
 641        is meant to be interpreted by the shell.  The order of preference
 642        is the `$GIT_PAGER` environment variable, then `core.pager`
 643        configuration, then `$PAGER`, and then the default chosen at
 644        compile time (usually 'less').
 645+
 646When the `LESS` environment variable is unset, Git sets it to `FRX`
 647(if `LESS` environment variable is set, Git does not change it at
 648all).  If you want to selectively override Git's default setting
 649for `LESS`, you can set `core.pager` to e.g. `less -S`.  This will
 650be passed to the shell by Git, which will translate the final
 651command to `LESS=FRX less -S`. The environment does not set the
 652`S` option but the command line does, instructing less to truncate
 653long lines. Similarly, setting `core.pager` to `less -+F` will
 654deactivate the `F` option specified by the environment from the
 655command-line, deactivating the "quit if one screen" behavior of
 656`less`.  One can specifically activate some flags for particular
 657commands: for example, setting `pager.blame` to `less -S` enables
 658line truncation only for `git blame`.
 659+
 660Likewise, when the `LV` environment variable is unset, Git sets it
 661to `-c`.  You can override this setting by exporting `LV` with
 662another value or setting `core.pager` to `lv +c`.
 663
 664core.whitespace::
 665        A comma separated list of common whitespace problems to
 666        notice.  'git diff' will use `color.diff.whitespace` to
 667        highlight them, and 'git apply --whitespace=error' will
 668        consider them as errors.  You can prefix `-` to disable
 669        any of them (e.g. `-trailing-space`):
 670+
 671* `blank-at-eol` treats trailing whitespaces at the end of the line
 672  as an error (enabled by default).
 673* `space-before-tab` treats a space character that appears immediately
 674  before a tab character in the initial indent part of the line as an
 675  error (enabled by default).
 676* `indent-with-non-tab` treats a line that is indented with space
 677  characters instead of the equivalent tabs as an error (not enabled by
 678  default).
 679* `tab-in-indent` treats a tab character in the initial indent part of
 680  the line as an error (not enabled by default).
 681* `blank-at-eof` treats blank lines added at the end of file as an error
 682  (enabled by default).
 683* `trailing-space` is a short-hand to cover both `blank-at-eol` and
 684  `blank-at-eof`.
 685* `cr-at-eol` treats a carriage-return at the end of line as
 686  part of the line terminator, i.e. with it, `trailing-space`
 687  does not trigger if the character before such a carriage-return
 688  is not a whitespace (not enabled by default).
 689* `tabwidth=<n>` tells how many character positions a tab occupies; this
 690  is relevant for `indent-with-non-tab` and when Git fixes `tab-in-indent`
 691  errors. The default tab width is 8. Allowed values are 1 to 63.
 692
 693core.fsyncObjectFiles::
 694        This boolean will enable 'fsync()' when writing object files.
 695+
 696This is a total waste of time and effort on a filesystem that orders
 697data writes properly, but can be useful for filesystems that do not use
 698journalling (traditional UNIX filesystems) or that only journal metadata
 699and not file contents (OS X's HFS+, or Linux ext3 with "data=writeback").
 700
 701core.preloadIndex::
 702        Enable parallel index preload for operations like 'git diff'
 703+
 704This can speed up operations like 'git diff' and 'git status' especially
 705on filesystems like NFS that have weak caching semantics and thus
 706relatively high IO latencies.  When enabled, Git will do the
 707index comparison to the filesystem data in parallel, allowing
 708overlapping IO's.  Defaults to true.
 709
 710core.createObject::
 711        You can set this to 'link', in which case a hardlink followed by
 712        a delete of the source are used to make sure that object creation
 713        will not overwrite existing objects.
 714+
 715On some file system/operating system combinations, this is unreliable.
 716Set this config setting to 'rename' there; However, This will remove the
 717check that makes sure that existing object files will not get overwritten.
 718
 719core.notesRef::
 720        When showing commit messages, also show notes which are stored in
 721        the given ref.  The ref must be fully qualified.  If the given
 722        ref does not exist, it is not an error but means that no
 723        notes should be printed.
 724+
 725This setting defaults to "refs/notes/commits", and it can be overridden by
 726the 'GIT_NOTES_REF' environment variable.  See linkgit:git-notes[1].
 727
 728core.sparseCheckout::
 729        Enable "sparse checkout" feature. See section "Sparse checkout" in
 730        linkgit:git-read-tree[1] for more information.
 731
 732core.abbrev::
 733        Set the length object names are abbreviated to.  If unspecified,
 734        many commands abbreviate to 7 hexdigits, which may not be enough
 735        for abbreviated object names to stay unique for sufficiently long
 736        time.
 737
 738add.ignoreErrors::
 739add.ignore-errors (deprecated)::
 740        Tells 'git add' to continue adding files when some files cannot be
 741        added due to indexing errors. Equivalent to the '--ignore-errors'
 742        option of linkgit:git-add[1].  `add.ignore-errors` is deprecated,
 743        as it does not follow the usual naming convention for configuration
 744        variables.
 745
 746alias.*::
 747        Command aliases for the linkgit:git[1] command wrapper - e.g.
 748        after defining "alias.last = cat-file commit HEAD", the invocation
 749        "git last" is equivalent to "git cat-file commit HEAD". To avoid
 750        confusion and troubles with script usage, aliases that
 751        hide existing Git commands are ignored. Arguments are split by
 752        spaces, the usual shell quoting and escaping is supported.
 753        A quote pair or a backslash can be used to quote them.
 754+
 755If the alias expansion is prefixed with an exclamation point,
 756it will be treated as a shell command.  For example, defining
 757"alias.new = !gitk --all --not ORIG_HEAD", the invocation
 758"git new" is equivalent to running the shell command
 759"gitk --all --not ORIG_HEAD".  Note that shell commands will be
 760executed from the top-level directory of a repository, which may
 761not necessarily be the current directory.
 762'GIT_PREFIX' is set as returned by running 'git rev-parse --show-prefix'
 763from the original current directory. See linkgit:git-rev-parse[1].
 764
 765am.keepcr::
 766        If true, git-am will call git-mailsplit for patches in mbox format
 767        with parameter '--keep-cr'. In this case git-mailsplit will
 768        not remove `\r` from lines ending with `\r\n`. Can be overridden
 769        by giving '--no-keep-cr' from the command line.
 770        See linkgit:git-am[1], linkgit:git-mailsplit[1].
 771
 772am.threeWay::
 773        By default, `git am` will fail if the patch does not apply cleanly. When
 774        set to true, this setting tells `git am` to fall back on 3-way merge if
 775        the patch records the identity of blobs it is supposed to apply to and
 776        we have those blobs available locally (equivalent to giving the `--3way`
 777        option from the command line). Defaults to `false`.
 778        See linkgit:git-am[1].
 779
 780apply.ignoreWhitespace::
 781        When set to 'change', tells 'git apply' to ignore changes in
 782        whitespace, in the same way as the '--ignore-space-change'
 783        option.
 784        When set to one of: no, none, never, false tells 'git apply' to
 785        respect all whitespace differences.
 786        See linkgit:git-apply[1].
 787
 788apply.whitespace::
 789        Tells 'git apply' how to handle whitespaces, in the same way
 790        as the '--whitespace' option. See linkgit:git-apply[1].
 791
 792branch.autoSetupMerge::
 793        Tells 'git branch' and 'git checkout' to set up new branches
 794        so that linkgit:git-pull[1] will appropriately merge from the
 795        starting point branch. Note that even if this option is not set,
 796        this behavior can be chosen per-branch using the `--track`
 797        and `--no-track` options. The valid settings are: `false` -- no
 798        automatic setup is done; `true` -- automatic setup is done when the
 799        starting point is a remote-tracking branch; `always` --
 800        automatic setup is done when the starting point is either a
 801        local branch or remote-tracking
 802        branch. This option defaults to true.
 803
 804branch.autoSetupRebase::
 805        When a new branch is created with 'git branch' or 'git checkout'
 806        that tracks another branch, this variable tells Git to set
 807        up pull to rebase instead of merge (see "branch.<name>.rebase").
 808        When `never`, rebase is never automatically set to true.
 809        When `local`, rebase is set to true for tracked branches of
 810        other local branches.
 811        When `remote`, rebase is set to true for tracked branches of
 812        remote-tracking branches.
 813        When `always`, rebase will be set to true for all tracking
 814        branches.
 815        See "branch.autoSetupMerge" for details on how to set up a
 816        branch to track another branch.
 817        This option defaults to never.
 818
 819branch.<name>.remote::
 820        When on branch <name>, it tells 'git fetch' and 'git push'
 821        which remote to fetch from/push to.  The remote to push to
 822        may be overridden with `remote.pushDefault` (for all branches).
 823        The remote to push to, for the current branch, may be further
 824        overridden by `branch.<name>.pushRemote`.  If no remote is
 825        configured, or if you are not on any branch, it defaults to
 826        `origin` for fetching and `remote.pushDefault` for pushing.
 827        Additionally, `.` (a period) is the current local repository
 828        (a dot-repository), see `branch.<name>.merge`'s final note below.
 829
 830branch.<name>.pushRemote::
 831        When on branch <name>, it overrides `branch.<name>.remote` for
 832        pushing.  It also overrides `remote.pushDefault` for pushing
 833        from branch <name>.  When you pull from one place (e.g. your
 834        upstream) and push to another place (e.g. your own publishing
 835        repository), you would want to set `remote.pushDefault` to
 836        specify the remote to push to for all branches, and use this
 837        option to override it for a specific branch.
 838
 839branch.<name>.merge::
 840        Defines, together with branch.<name>.remote, the upstream branch
 841        for the given branch. It tells 'git fetch'/'git pull'/'git rebase' which
 842        branch to merge and can also affect 'git push' (see push.default).
 843        When in branch <name>, it tells 'git fetch' the default
 844        refspec to be marked for merging in FETCH_HEAD. The value is
 845        handled like the remote part of a refspec, and must match a
 846        ref which is fetched from the remote given by
 847        "branch.<name>.remote".
 848        The merge information is used by 'git pull' (which at first calls
 849        'git fetch') to lookup the default branch for merging. Without
 850        this option, 'git pull' defaults to merge the first refspec fetched.
 851        Specify multiple values to get an octopus merge.
 852        If you wish to setup 'git pull' so that it merges into <name> from
 853        another branch in the local repository, you can point
 854        branch.<name>.merge to the desired branch, and use the relative path
 855        setting `.` (a period) for branch.<name>.remote.
 856
 857branch.<name>.mergeOptions::
 858        Sets default options for merging into branch <name>. The syntax and
 859        supported options are the same as those of linkgit:git-merge[1], but
 860        option values containing whitespace characters are currently not
 861        supported.
 862
 863branch.<name>.rebase::
 864        When true, rebase the branch <name> on top of the fetched branch,
 865        instead of merging the default branch from the default remote when
 866        "git pull" is run. See "pull.rebase" for doing this in a non
 867        branch-specific manner.
 868+
 869        When preserve, also pass `--preserve-merges` along to 'git rebase'
 870        so that locally committed merge commits will not be flattened
 871        by running 'git pull'.
 872+
 873*NOTE*: this is a possibly dangerous operation; do *not* use
 874it unless you understand the implications (see linkgit:git-rebase[1]
 875for details).
 876
 877branch.<name>.description::
 878        Branch description, can be edited with
 879        `git branch --edit-description`. Branch description is
 880        automatically added in the format-patch cover letter or
 881        request-pull summary.
 882
 883browser.<tool>.cmd::
 884        Specify the command to invoke the specified browser. The
 885        specified command is evaluated in shell with the URLs passed
 886        as arguments. (See linkgit:git-web{litdd}browse[1].)
 887
 888browser.<tool>.path::
 889        Override the path for the given tool that may be used to
 890        browse HTML help (see '-w' option in linkgit:git-help[1]) or a
 891        working repository in gitweb (see linkgit:git-instaweb[1]).
 892
 893clean.requireForce::
 894        A boolean to make git-clean do nothing unless given -f,
 895        -i or -n.   Defaults to true.
 896
 897color.branch::
 898        A boolean to enable/disable color in the output of
 899        linkgit:git-branch[1]. May be set to `always`,
 900        `false` (or `never`) or `auto` (or `true`), in which case colors are used
 901        only when the output is to a terminal. Defaults to false.
 902
 903color.branch.<slot>::
 904        Use customized color for branch coloration. `<slot>` is one of
 905        `current` (the current branch), `local` (a local branch),
 906        `remote` (a remote-tracking branch in refs/remotes/),
 907        `upstream` (upstream tracking branch), `plain` (other
 908        refs).
 909
 910color.diff::
 911        Whether to use ANSI escape sequences to add color to patches.
 912        If this is set to `always`, linkgit:git-diff[1],
 913        linkgit:git-log[1], and linkgit:git-show[1] will use color
 914        for all patches.  If it is set to `true` or `auto`, those
 915        commands will only use color when output is to the terminal.
 916        Defaults to false.
 917+
 918This does not affect linkgit:git-format-patch[1] or the
 919'git-diff-{asterisk}' plumbing commands.  Can be overridden on the
 920command line with the `--color[=<when>]` option.
 921
 922color.diff.<slot>::
 923        Use customized color for diff colorization.  `<slot>` specifies
 924        which part of the patch to use the specified color, and is one
 925        of `context` (context text - `plain` is a historical synonym),
 926        `meta` (metainformation), `frag`
 927        (hunk header), 'func' (function in hunk header), `old` (removed lines),
 928        `new` (added lines), `commit` (commit headers), or `whitespace`
 929        (highlighting whitespace errors).
 930
 931color.decorate.<slot>::
 932        Use customized color for 'git log --decorate' output.  `<slot>` is one
 933        of `branch`, `remoteBranch`, `tag`, `stash` or `HEAD` for local
 934        branches, remote-tracking branches, tags, stash and HEAD, respectively.
 935
 936color.grep::
 937        When set to `always`, always highlight matches.  When `false` (or
 938        `never`), never.  When set to `true` or `auto`, use color only
 939        when the output is written to the terminal.  Defaults to `false`.
 940
 941color.grep.<slot>::
 942        Use customized color for grep colorization.  `<slot>` specifies which
 943        part of the line to use the specified color, and is one of
 944+
 945--
 946`context`;;
 947        non-matching text in context lines (when using `-A`, `-B`, or `-C`)
 948`filename`;;
 949        filename prefix (when not using `-h`)
 950`function`;;
 951        function name lines (when using `-p`)
 952`linenumber`;;
 953        line number prefix (when using `-n`)
 954`match`;;
 955        matching text (same as setting `matchContext` and `matchSelected`)
 956`matchContext`;;
 957        matching text in context lines
 958`matchSelected`;;
 959        matching text in selected lines
 960`selected`;;
 961        non-matching text in selected lines
 962`separator`;;
 963        separators between fields on a line (`:`, `-`, and `=`)
 964        and between hunks (`--`)
 965--
 966
 967color.interactive::
 968        When set to `always`, always use colors for interactive prompts
 969        and displays (such as those used by "git-add --interactive" and
 970        "git-clean --interactive"). When false (or `never`), never.
 971        When set to `true` or `auto`, use colors only when the output is
 972        to the terminal. Defaults to false.
 973
 974color.interactive.<slot>::
 975        Use customized color for 'git add --interactive' and 'git clean
 976        --interactive' output. `<slot>` may be `prompt`, `header`, `help`
 977        or `error`, for four distinct types of normal output from
 978        interactive commands.
 979
 980color.pager::
 981        A boolean to enable/disable colored output when the pager is in
 982        use (default is true).
 983
 984color.showBranch::
 985        A boolean to enable/disable color in the output of
 986        linkgit:git-show-branch[1]. May be set to `always`,
 987        `false` (or `never`) or `auto` (or `true`), in which case colors are used
 988        only when the output is to a terminal. Defaults to false.
 989
 990color.status::
 991        A boolean to enable/disable color in the output of
 992        linkgit:git-status[1]. May be set to `always`,
 993        `false` (or `never`) or `auto` (or `true`), in which case colors are used
 994        only when the output is to a terminal. Defaults to false.
 995
 996color.status.<slot>::
 997        Use customized color for status colorization. `<slot>` is
 998        one of `header` (the header text of the status message),
 999        `added` or `updated` (files which are added but not committed),
1000        `changed` (files which are changed but not added in the index),
1001        `untracked` (files which are not tracked by Git),
1002        `branch` (the current branch),
1003        `nobranch` (the color the 'no branch' warning is shown in, defaulting
1004        to red), or
1005        `unmerged` (files which have unmerged changes).
1006
1007color.ui::
1008        This variable determines the default value for variables such
1009        as `color.diff` and `color.grep` that control the use of color
1010        per command family. Its scope will expand as more commands learn
1011        configuration to set a default for the `--color` option.  Set it
1012        to `false` or `never` if you prefer Git commands not to use
1013        color unless enabled explicitly with some other configuration
1014        or the `--color` option. Set it to `always` if you want all
1015        output not intended for machine consumption to use color, to
1016        `true` or `auto` (this is the default since Git 1.8.4) if you
1017        want such output to use color when written to the terminal.
1018
1019column.ui::
1020        Specify whether supported commands should output in columns.
1021        This variable consists of a list of tokens separated by spaces
1022        or commas:
1023+
1024These options control when the feature should be enabled
1025(defaults to 'never'):
1026+
1027--
1028`always`;;
1029        always show in columns
1030`never`;;
1031        never show in columns
1032`auto`;;
1033        show in columns if the output is to the terminal
1034--
1035+
1036These options control layout (defaults to 'column').  Setting any
1037of these implies 'always' if none of 'always', 'never', or 'auto' are
1038specified.
1039+
1040--
1041`column`;;
1042        fill columns before rows
1043`row`;;
1044        fill rows before columns
1045`plain`;;
1046        show in one column
1047--
1048+
1049Finally, these options can be combined with a layout option (defaults
1050to 'nodense'):
1051+
1052--
1053`dense`;;
1054        make unequal size columns to utilize more space
1055`nodense`;;
1056        make equal size columns
1057--
1058
1059column.branch::
1060        Specify whether to output branch listing in `git branch` in columns.
1061        See `column.ui` for details.
1062
1063column.clean::
1064        Specify the layout when list items in `git clean -i`, which always
1065        shows files and directories in columns. See `column.ui` for details.
1066
1067column.status::
1068        Specify whether to output untracked files in `git status` in columns.
1069        See `column.ui` for details.
1070
1071column.tag::
1072        Specify whether to output tag listing in `git tag` in columns.
1073        See `column.ui` for details.
1074
1075commit.cleanup::
1076        This setting overrides the default of the `--cleanup` option in
1077        `git commit`. See linkgit:git-commit[1] for details. Changing the
1078        default can be useful when you always want to keep lines that begin
1079        with comment character `#` in your log message, in which case you
1080        would do `git config commit.cleanup whitespace` (note that you will
1081        have to remove the help lines that begin with `#` in the commit log
1082        template yourself, if you do this).
1083
1084commit.gpgSign::
1085
1086        A boolean to specify whether all commits should be GPG signed.
1087        Use of this option when doing operations such as rebase can
1088        result in a large number of commits being signed. It may be
1089        convenient to use an agent to avoid typing your GPG passphrase
1090        several times.
1091
1092commit.status::
1093        A boolean to enable/disable inclusion of status information in the
1094        commit message template when using an editor to prepare the commit
1095        message.  Defaults to true.
1096
1097commit.template::
1098        Specify a file to use as the template for new commit messages.
1099        "`~/`" is expanded to the value of `$HOME` and "`~user/`" to the
1100        specified user's home directory.
1101
1102credential.helper::
1103        Specify an external helper to be called when a username or
1104        password credential is needed; the helper may consult external
1105        storage to avoid prompting the user for the credentials. See
1106        linkgit:gitcredentials[7] for details.
1107
1108credential.useHttpPath::
1109        When acquiring credentials, consider the "path" component of an http
1110        or https URL to be important. Defaults to false. See
1111        linkgit:gitcredentials[7] for more information.
1112
1113credential.username::
1114        If no username is set for a network authentication, use this username
1115        by default. See credential.<context>.* below, and
1116        linkgit:gitcredentials[7].
1117
1118credential.<url>.*::
1119        Any of the credential.* options above can be applied selectively to
1120        some credentials. For example "credential.https://example.com.username"
1121        would set the default username only for https connections to
1122        example.com. See linkgit:gitcredentials[7] for details on how URLs are
1123        matched.
1124
1125include::diff-config.txt[]
1126
1127difftool.<tool>.path::
1128        Override the path for the given tool.  This is useful in case
1129        your tool is not in the PATH.
1130
1131difftool.<tool>.cmd::
1132        Specify the command to invoke the specified diff tool.
1133        The specified command is evaluated in shell with the following
1134        variables available:  'LOCAL' is set to the name of the temporary
1135        file containing the contents of the diff pre-image and 'REMOTE'
1136        is set to the name of the temporary file containing the contents
1137        of the diff post-image.
1138
1139difftool.prompt::
1140        Prompt before each invocation of the diff tool.
1141
1142fetch.recurseSubmodules::
1143        This option can be either set to a boolean value or to 'on-demand'.
1144        Setting it to a boolean changes the behavior of fetch and pull to
1145        unconditionally recurse into submodules when set to true or to not
1146        recurse at all when set to false. When set to 'on-demand' (the default
1147        value), fetch and pull will only recurse into a populated submodule
1148        when its superproject retrieves a commit that updates the submodule's
1149        reference.
1150
1151fetch.fsckObjects::
1152        If it is set to true, git-fetch-pack will check all fetched
1153        objects. It will abort in the case of a malformed object or a
1154        broken link. The result of an abort are only dangling objects.
1155        Defaults to false. If not set, the value of `transfer.fsckObjects`
1156        is used instead.
1157
1158fetch.unpackLimit::
1159        If the number of objects fetched over the Git native
1160        transfer is below this
1161        limit, then the objects will be unpacked into loose object
1162        files. However if the number of received objects equals or
1163        exceeds this limit then the received pack will be stored as
1164        a pack, after adding any missing delta bases.  Storing the
1165        pack from a push can make the push operation complete faster,
1166        especially on slow filesystems.  If not set, the value of
1167        `transfer.unpackLimit` is used instead.
1168
1169fetch.prune::
1170        If true, fetch will automatically behave as if the `--prune`
1171        option was given on the command line.  See also `remote.<name>.prune`.
1172
1173format.attach::
1174        Enable multipart/mixed attachments as the default for
1175        'format-patch'.  The value can also be a double quoted string
1176        which will enable attachments as the default and set the
1177        value as the boundary.  See the --attach option in
1178        linkgit:git-format-patch[1].
1179
1180format.numbered::
1181        A boolean which can enable or disable sequence numbers in patch
1182        subjects.  It defaults to "auto" which enables it only if there
1183        is more than one patch.  It can be enabled or disabled for all
1184        messages by setting it to "true" or "false".  See --numbered
1185        option in linkgit:git-format-patch[1].
1186
1187format.headers::
1188        Additional email headers to include in a patch to be submitted
1189        by mail.  See linkgit:git-format-patch[1].
1190
1191format.to::
1192format.cc::
1193        Additional recipients to include in a patch to be submitted
1194        by mail.  See the --to and --cc options in
1195        linkgit:git-format-patch[1].
1196
1197format.subjectPrefix::
1198        The default for format-patch is to output files with the '[PATCH]'
1199        subject prefix. Use this variable to change that prefix.
1200
1201format.signature::
1202        The default for format-patch is to output a signature containing
1203        the Git version number. Use this variable to change that default.
1204        Set this variable to the empty string ("") to suppress
1205        signature generation.
1206
1207format.signatureFile::
1208        Works just like format.signature except the contents of the
1209        file specified by this variable will be used as the signature.
1210
1211format.suffix::
1212        The default for format-patch is to output files with the suffix
1213        `.patch`. Use this variable to change that suffix (make sure to
1214        include the dot if you want it).
1215
1216format.pretty::
1217        The default pretty format for log/show/whatchanged command,
1218        See linkgit:git-log[1], linkgit:git-show[1],
1219        linkgit:git-whatchanged[1].
1220
1221format.thread::
1222        The default threading style for 'git format-patch'.  Can be
1223        a boolean value, or `shallow` or `deep`.  `shallow` threading
1224        makes every mail a reply to the head of the series,
1225        where the head is chosen from the cover letter, the
1226        `--in-reply-to`, and the first patch mail, in this order.
1227        `deep` threading makes every mail a reply to the previous one.
1228        A true boolean value is the same as `shallow`, and a false
1229        value disables threading.
1230
1231format.signOff::
1232        A boolean value which lets you enable the `-s/--signoff` option of
1233        format-patch by default. *Note:* Adding the Signed-off-by: line to a
1234        patch should be a conscious act and means that you certify you have
1235        the rights to submit this work under the same open source license.
1236        Please see the 'SubmittingPatches' document for further discussion.
1237
1238format.coverLetter::
1239        A boolean that controls whether to generate a cover-letter when
1240        format-patch is invoked, but in addition can be set to "auto", to
1241        generate a cover-letter only when there's more than one patch.
1242
1243filter.<driver>.clean::
1244        The command which is used to convert the content of a worktree
1245        file to a blob upon checkin.  See linkgit:gitattributes[5] for
1246        details.
1247
1248filter.<driver>.smudge::
1249        The command which is used to convert the content of a blob
1250        object to a worktree file upon checkout.  See
1251        linkgit:gitattributes[5] for details.
1252
1253gc.aggressiveDepth::
1254        The depth parameter used in the delta compression
1255        algorithm used by 'git gc --aggressive'.  This defaults
1256        to 250.
1257
1258gc.aggressiveWindow::
1259        The window size parameter used in the delta compression
1260        algorithm used by 'git gc --aggressive'.  This defaults
1261        to 250.
1262
1263gc.auto::
1264        When there are approximately more than this many loose
1265        objects in the repository, `git gc --auto` will pack them.
1266        Some Porcelain commands use this command to perform a
1267        light-weight garbage collection from time to time.  The
1268        default value is 6700.  Setting this to 0 disables it.
1269
1270gc.autoPackLimit::
1271        When there are more than this many packs that are not
1272        marked with `*.keep` file in the repository, `git gc
1273        --auto` consolidates them into one larger pack.  The
1274        default value is 50.  Setting this to 0 disables it.
1275
1276gc.autoDetach::
1277        Make `git gc --auto` return immediately and run in background
1278        if the system supports it. Default is true.
1279
1280gc.packRefs::
1281        Running `git pack-refs` in a repository renders it
1282        unclonable by Git versions prior to 1.5.1.2 over dumb
1283        transports such as HTTP.  This variable determines whether
1284        'git gc' runs `git pack-refs`. This can be set to `notbare`
1285        to enable it within all non-bare repos or it can be set to a
1286        boolean value.  The default is `true`.
1287
1288gc.pruneExpire::
1289        When 'git gc' is run, it will call 'prune --expire 2.weeks.ago'.
1290        Override the grace period with this config variable.  The value
1291        "now" may be used to disable this  grace period and always prune
1292        unreachable objects immediately.
1293
1294gc.pruneWorktreesExpire::
1295        When 'git gc' is run, it will call
1296        'prune --worktrees --expire 3.months.ago'.
1297        Override the grace period with this config variable. The value
1298        "now" may be used to disable the grace period and prune
1299        $GIT_DIR/worktrees immediately.
1300
1301gc.reflogExpire::
1302gc.<pattern>.reflogExpire::
1303        'git reflog expire' removes reflog entries older than
1304        this time; defaults to 90 days.  With "<pattern>" (e.g.
1305        "refs/stash") in the middle the setting applies only to
1306        the refs that match the <pattern>.
1307
1308gc.reflogExpireUnreachable::
1309gc.<ref>.reflogExpireUnreachable::
1310        'git reflog expire' removes reflog entries older than
1311        this time and are not reachable from the current tip;
1312        defaults to 30 days.  With "<pattern>" (e.g. "refs/stash")
1313        in the middle, the setting applies only to the refs that
1314        match the <pattern>.
1315
1316gc.rerereResolved::
1317        Records of conflicted merge you resolved earlier are
1318        kept for this many days when 'git rerere gc' is run.
1319        The default is 60 days.  See linkgit:git-rerere[1].
1320
1321gc.rerereUnresolved::
1322        Records of conflicted merge you have not resolved are
1323        kept for this many days when 'git rerere gc' is run.
1324        The default is 15 days.  See linkgit:git-rerere[1].
1325
1326gitcvs.commitMsgAnnotation::
1327        Append this string to each commit message. Set to empty string
1328        to disable this feature. Defaults to "via git-CVS emulator".
1329
1330gitcvs.enabled::
1331        Whether the CVS server interface is enabled for this repository.
1332        See linkgit:git-cvsserver[1].
1333
1334gitcvs.logFile::
1335        Path to a log file where the CVS server interface well... logs
1336        various stuff. See linkgit:git-cvsserver[1].
1337
1338gitcvs.usecrlfattr::
1339        If true, the server will look up the end-of-line conversion
1340        attributes for files to determine the '-k' modes to use. If
1341        the attributes force Git to treat a file as text,
1342        the '-k' mode will be left blank so CVS clients will
1343        treat it as text. If they suppress text conversion, the file
1344        will be set with '-kb' mode, which suppresses any newline munging
1345        the client might otherwise do. If the attributes do not allow
1346        the file type to be determined, then 'gitcvs.allBinary' is
1347        used. See linkgit:gitattributes[5].
1348
1349gitcvs.allBinary::
1350        This is used if 'gitcvs.usecrlfattr' does not resolve
1351        the correct '-kb' mode to use. If true, all
1352        unresolved files are sent to the client in
1353        mode '-kb'. This causes the client to treat them
1354        as binary files, which suppresses any newline munging it
1355        otherwise might do. Alternatively, if it is set to "guess",
1356        then the contents of the file are examined to decide if
1357        it is binary, similar to 'core.autocrlf'.
1358
1359gitcvs.dbName::
1360        Database used by git-cvsserver to cache revision information
1361        derived from the Git repository. The exact meaning depends on the
1362        used database driver, for SQLite (which is the default driver) this
1363        is a filename. Supports variable substitution (see
1364        linkgit:git-cvsserver[1] for details). May not contain semicolons (`;`).
1365        Default: '%Ggitcvs.%m.sqlite'
1366
1367gitcvs.dbDriver::
1368        Used Perl DBI driver. You can specify any available driver
1369        for this here, but it might not work. git-cvsserver is tested
1370        with 'DBD::SQLite', reported to work with 'DBD::Pg', and
1371        reported *not* to work with 'DBD::mysql'. Experimental feature.
1372        May not contain double colons (`:`). Default: 'SQLite'.
1373        See linkgit:git-cvsserver[1].
1374
1375gitcvs.dbUser, gitcvs.dbPass::
1376        Database user and password. Only useful if setting 'gitcvs.dbDriver',
1377        since SQLite has no concept of database users and/or passwords.
1378        'gitcvs.dbUser' supports variable substitution (see
1379        linkgit:git-cvsserver[1] for details).
1380
1381gitcvs.dbTableNamePrefix::
1382        Database table name prefix.  Prepended to the names of any
1383        database tables used, allowing a single database to be used
1384        for several repositories.  Supports variable substitution (see
1385        linkgit:git-cvsserver[1] for details).  Any non-alphabetic
1386        characters will be replaced with underscores.
1387
1388All gitcvs variables except for 'gitcvs.usecrlfattr' and
1389'gitcvs.allBinary' can also be specified as
1390'gitcvs.<access_method>.<varname>' (where 'access_method'
1391is one of "ext" and "pserver") to make them apply only for the given
1392access method.
1393
1394gitweb.category::
1395gitweb.description::
1396gitweb.owner::
1397gitweb.url::
1398        See linkgit:gitweb[1] for description.
1399
1400gitweb.avatar::
1401gitweb.blame::
1402gitweb.grep::
1403gitweb.highlight::
1404gitweb.patches::
1405gitweb.pickaxe::
1406gitweb.remote_heads::
1407gitweb.showSizes::
1408gitweb.snapshot::
1409        See linkgit:gitweb.conf[5] for description.
1410
1411grep.lineNumber::
1412        If set to true, enable '-n' option by default.
1413
1414grep.patternType::
1415        Set the default matching behavior. Using a value of 'basic', 'extended',
1416        'fixed', or 'perl' will enable the '--basic-regexp', '--extended-regexp',
1417        '--fixed-strings', or '--perl-regexp' option accordingly, while the
1418        value 'default' will return to the default matching behavior.
1419
1420grep.extendedRegexp::
1421        If set to true, enable '--extended-regexp' option by default. This
1422        option is ignored when the 'grep.patternType' option is set to a value
1423        other than 'default'.
1424
1425gpg.program::
1426        Use this custom program instead of "gpg" found on $PATH when
1427        making or verifying a PGP signature. The program must support the
1428        same command-line interface as GPG, namely, to verify a detached
1429        signature, "gpg --verify $file - <$signature" is run, and the
1430        program is expected to signal a good signature by exiting with
1431        code 0, and to generate an ASCII-armored detached signature, the
1432        standard input of "gpg -bsau $key" is fed with the contents to be
1433        signed, and the program is expected to send the result to its
1434        standard output.
1435
1436gui.commitMsgWidth::
1437        Defines how wide the commit message window is in the
1438        linkgit:git-gui[1]. "75" is the default.
1439
1440gui.diffContext::
1441        Specifies how many context lines should be used in calls to diff
1442        made by the linkgit:git-gui[1]. The default is "5".
1443
1444gui.displayUntracked::
1445        Determines if linkgit::git-gui[1] shows untracked files
1446        in the file list. The default is "true".
1447
1448gui.encoding::
1449        Specifies the default encoding to use for displaying of
1450        file contents in linkgit:git-gui[1] and linkgit:gitk[1].
1451        It can be overridden by setting the 'encoding' attribute
1452        for relevant files (see linkgit:gitattributes[5]).
1453        If this option is not set, the tools default to the
1454        locale encoding.
1455
1456gui.matchTrackingBranch::
1457        Determines if new branches created with linkgit:git-gui[1] should
1458        default to tracking remote branches with matching names or
1459        not. Default: "false".
1460
1461gui.newBranchTemplate::
1462        Is used as suggested name when creating new branches using the
1463        linkgit:git-gui[1].
1464
1465gui.pruneDuringFetch::
1466        "true" if linkgit:git-gui[1] should prune remote-tracking branches when
1467        performing a fetch. The default value is "false".
1468
1469gui.trustmtime::
1470        Determines if linkgit:git-gui[1] should trust the file modification
1471        timestamp or not. By default the timestamps are not trusted.
1472
1473gui.spellingDictionary::
1474        Specifies the dictionary used for spell checking commit messages in
1475        the linkgit:git-gui[1]. When set to "none" spell checking is turned
1476        off.
1477
1478gui.fastCopyBlame::
1479        If true, 'git gui blame' uses `-C` instead of `-C -C` for original
1480        location detection. It makes blame significantly faster on huge
1481        repositories at the expense of less thorough copy detection.
1482
1483gui.copyBlameThreshold::
1484        Specifies the threshold to use in 'git gui blame' original location
1485        detection, measured in alphanumeric characters. See the
1486        linkgit:git-blame[1] manual for more information on copy detection.
1487
1488gui.blamehistoryctx::
1489        Specifies the radius of history context in days to show in
1490        linkgit:gitk[1] for the selected commit, when the `Show History
1491        Context` menu item is invoked from 'git gui blame'. If this
1492        variable is set to zero, the whole history is shown.
1493
1494guitool.<name>.cmd::
1495        Specifies the shell command line to execute when the corresponding item
1496        of the linkgit:git-gui[1] `Tools` menu is invoked. This option is
1497        mandatory for every tool. The command is executed from the root of
1498        the working directory, and in the environment it receives the name of
1499        the tool as 'GIT_GUITOOL', the name of the currently selected file as
1500        'FILENAME', and the name of the current branch as 'CUR_BRANCH' (if
1501        the head is detached, 'CUR_BRANCH' is empty).
1502
1503guitool.<name>.needsFile::
1504        Run the tool only if a diff is selected in the GUI. It guarantees
1505        that 'FILENAME' is not empty.
1506
1507guitool.<name>.noConsole::
1508        Run the command silently, without creating a window to display its
1509        output.
1510
1511guitool.<name>.noRescan::
1512        Don't rescan the working directory for changes after the tool
1513        finishes execution.
1514
1515guitool.<name>.confirm::
1516        Show a confirmation dialog before actually running the tool.
1517
1518guitool.<name>.argPrompt::
1519        Request a string argument from the user, and pass it to the tool
1520        through the 'ARGS' environment variable. Since requesting an
1521        argument implies confirmation, the 'confirm' option has no effect
1522        if this is enabled. If the option is set to 'true', 'yes', or '1',
1523        the dialog uses a built-in generic prompt; otherwise the exact
1524        value of the variable is used.
1525
1526guitool.<name>.revPrompt::
1527        Request a single valid revision from the user, and set the
1528        'REVISION' environment variable. In other aspects this option
1529        is similar to 'argPrompt', and can be used together with it.
1530
1531guitool.<name>.revUnmerged::
1532        Show only unmerged branches in the 'revPrompt' subdialog.
1533        This is useful for tools similar to merge or rebase, but not
1534        for things like checkout or reset.
1535
1536guitool.<name>.title::
1537        Specifies the title to use for the prompt dialog. The default
1538        is the tool name.
1539
1540guitool.<name>.prompt::
1541        Specifies the general prompt string to display at the top of
1542        the dialog, before subsections for 'argPrompt' and 'revPrompt'.
1543        The default value includes the actual command.
1544
1545help.browser::
1546        Specify the browser that will be used to display help in the
1547        'web' format. See linkgit:git-help[1].
1548
1549help.format::
1550        Override the default help format used by linkgit:git-help[1].
1551        Values 'man', 'info', 'web' and 'html' are supported. 'man' is
1552        the default. 'web' and 'html' are the same.
1553
1554help.autoCorrect::
1555        Automatically correct and execute mistyped commands after
1556        waiting for the given number of deciseconds (0.1 sec). If more
1557        than one command can be deduced from the entered text, nothing
1558        will be executed.  If the value of this option is negative,
1559        the corrected command will be executed immediately. If the
1560        value is 0 - the command will be just shown but not executed.
1561        This is the default.
1562
1563help.htmlPath::
1564        Specify the path where the HTML documentation resides. File system paths
1565        and URLs are supported. HTML pages will be prefixed with this path when
1566        help is displayed in the 'web' format. This defaults to the documentation
1567        path of your Git installation.
1568
1569http.proxy::
1570        Override the HTTP proxy, normally configured using the 'http_proxy',
1571        'https_proxy', and 'all_proxy' environment variables (see
1572        `curl(1)`).  This can be overridden on a per-remote basis; see
1573        remote.<name>.proxy
1574
1575http.cookieFile::
1576        File containing previously stored cookie lines which should be used
1577        in the Git http session, if they match the server. The file format
1578        of the file to read cookies from should be plain HTTP headers or
1579        the Netscape/Mozilla cookie file format (see linkgit:curl[1]).
1580        NOTE that the file specified with http.cookieFile is only used as
1581        input unless http.saveCookies is set.
1582
1583http.saveCookies::
1584        If set, store cookies received during requests to the file specified by
1585        http.cookieFile. Has no effect if http.cookieFile is unset.
1586
1587http.sslCipherList::
1588  A list of SSL ciphers to use when negotiating an SSL connection.
1589  The available ciphers depend on whether libcurl was built against
1590  NSS or OpenSSL and the particular configuration of the crypto
1591  library in use.  Internally this sets the 'CURLOPT_SSL_CIPHER_LIST'
1592  option; see the libcurl documentation for more details on the format
1593  of this list.
1594+
1595Can be overridden by the 'GIT_SSL_CIPHER_LIST' environment variable.
1596To force git to use libcurl's default cipher list and ignore any
1597explicit http.sslCipherList option, set 'GIT_SSL_CIPHER_LIST' to the
1598empty string.
1599
1600http.sslVerify::
1601        Whether to verify the SSL certificate when fetching or pushing
1602        over HTTPS. Can be overridden by the 'GIT_SSL_NO_VERIFY' environment
1603        variable.
1604
1605http.sslCert::
1606        File containing the SSL certificate when fetching or pushing
1607        over HTTPS. Can be overridden by the 'GIT_SSL_CERT' environment
1608        variable.
1609
1610http.sslKey::
1611        File containing the SSL private key when fetching or pushing
1612        over HTTPS. Can be overridden by the 'GIT_SSL_KEY' environment
1613        variable.
1614
1615http.sslCertPasswordProtected::
1616        Enable Git's password prompt for the SSL certificate.  Otherwise
1617        OpenSSL will prompt the user, possibly many times, if the
1618        certificate or private key is encrypted.  Can be overridden by the
1619        'GIT_SSL_CERT_PASSWORD_PROTECTED' environment variable.
1620
1621http.sslCAInfo::
1622        File containing the certificates to verify the peer with when
1623        fetching or pushing over HTTPS. Can be overridden by the
1624        'GIT_SSL_CAINFO' environment variable.
1625
1626http.sslCAPath::
1627        Path containing files with the CA certificates to verify the peer
1628        with when fetching or pushing over HTTPS. Can be overridden
1629        by the 'GIT_SSL_CAPATH' environment variable.
1630
1631http.sslTry::
1632        Attempt to use AUTH SSL/TLS and encrypted data transfers
1633        when connecting via regular FTP protocol. This might be needed
1634        if the FTP server requires it for security reasons or you wish
1635        to connect securely whenever remote FTP server supports it.
1636        Default is false since it might trigger certificate verification
1637        errors on misconfigured servers.
1638
1639http.maxRequests::
1640        How many HTTP requests to launch in parallel. Can be overridden
1641        by the 'GIT_HTTP_MAX_REQUESTS' environment variable. Default is 5.
1642
1643http.minSessions::
1644        The number of curl sessions (counted across slots) to be kept across
1645        requests. They will not be ended with curl_easy_cleanup() until
1646        http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
1647        value will be capped at 1. Defaults to 1.
1648
1649http.postBuffer::
1650        Maximum size in bytes of the buffer used by smart HTTP
1651        transports when POSTing data to the remote system.
1652        For requests larger than this buffer size, HTTP/1.1 and
1653        Transfer-Encoding: chunked is used to avoid creating a
1654        massive pack file locally.  Default is 1 MiB, which is
1655        sufficient for most requests.
1656
1657http.lowSpeedLimit, http.lowSpeedTime::
1658        If the HTTP transfer speed is less than 'http.lowSpeedLimit'
1659        for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
1660        Can be overridden by the 'GIT_HTTP_LOW_SPEED_LIMIT' and
1661        'GIT_HTTP_LOW_SPEED_TIME' environment variables.
1662
1663http.noEPSV::
1664        A boolean which disables using of EPSV ftp command by curl.
1665        This can helpful with some "poor" ftp servers which don't
1666        support EPSV mode. Can be overridden by the 'GIT_CURL_FTP_NO_EPSV'
1667        environment variable. Default is false (curl will use EPSV).
1668
1669http.userAgent::
1670        The HTTP USER_AGENT string presented to an HTTP server.  The default
1671        value represents the version of the client Git such as git/1.7.1.
1672        This option allows you to override this value to a more common value
1673        such as Mozilla/4.0.  This may be necessary, for instance, if
1674        connecting through a firewall that restricts HTTP connections to a set
1675        of common USER_AGENT strings (but not including those like git/1.7.1).
1676        Can be overridden by the 'GIT_HTTP_USER_AGENT' environment variable.
1677
1678http.<url>.*::
1679        Any of the http.* options above can be applied selectively to some URLs.
1680        For a config key to match a URL, each element of the config key is
1681        compared to that of the URL, in the following order:
1682+
1683--
1684. Scheme (e.g., `https` in `https://example.com/`). This field
1685  must match exactly between the config key and the URL.
1686
1687. Host/domain name (e.g., `example.com` in `https://example.com/`).
1688  This field must match exactly between the config key and the URL.
1689
1690. Port number (e.g., `8080` in `http://example.com:8080/`).
1691  This field must match exactly between the config key and the URL.
1692  Omitted port numbers are automatically converted to the correct
1693  default for the scheme before matching.
1694
1695. Path (e.g., `repo.git` in `https://example.com/repo.git`). The
1696  path field of the config key must match the path field of the URL
1697  either exactly or as a prefix of slash-delimited path elements.  This means
1698  a config key with path `foo/` matches URL path `foo/bar`.  A prefix can only
1699  match on a slash (`/`) boundary.  Longer matches take precedence (so a config
1700  key with path `foo/bar` is a better match to URL path `foo/bar` than a config
1701  key with just path `foo/`).
1702
1703. User name (e.g., `user` in `https://user@example.com/repo.git`). If
1704  the config key has a user name it must match the user name in the
1705  URL exactly. If the config key does not have a user name, that
1706  config key will match a URL with any user name (including none),
1707  but at a lower precedence than a config key with a user name.
1708--
1709+
1710The list above is ordered by decreasing precedence; a URL that matches
1711a config key's path is preferred to one that matches its user name. For example,
1712if the URL is `https://user@example.com/foo/bar` a config key match of
1713`https://example.com/foo` will be preferred over a config key match of
1714`https://user@example.com`.
1715+
1716All URLs are normalized before attempting any matching (the password part,
1717if embedded in the URL, is always ignored for matching purposes) so that
1718equivalent URLs that are simply spelled differently will match properly.
1719Environment variable settings always override any matches.  The URLs that are
1720matched against are those given directly to Git commands.  This means any URLs
1721visited as a result of a redirection do not participate in matching.
1722
1723i18n.commitEncoding::
1724        Character encoding the commit messages are stored in; Git itself
1725        does not care per se, but this information is necessary e.g. when
1726        importing commits from emails or in the gitk graphical history
1727        browser (and possibly at other places in the future or in other
1728        porcelains). See e.g. linkgit:git-mailinfo[1]. Defaults to 'utf-8'.
1729
1730i18n.logOutputEncoding::
1731        Character encoding the commit messages are converted to when
1732        running 'git log' and friends.
1733
1734imap::
1735        The configuration variables in the 'imap' section are described
1736        in linkgit:git-imap-send[1].
1737
1738index.version::
1739        Specify the version with which new index files should be
1740        initialized.  This does not affect existing repositories.
1741
1742init.templateDir::
1743        Specify the directory from which templates will be copied.
1744        (See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
1745
1746instaweb.browser::
1747        Specify the program that will be used to browse your working
1748        repository in gitweb. See linkgit:git-instaweb[1].
1749
1750instaweb.httpd::
1751        The HTTP daemon command-line to start gitweb on your working
1752        repository. See linkgit:git-instaweb[1].
1753
1754instaweb.local::
1755        If true the web server started by linkgit:git-instaweb[1] will
1756        be bound to the local IP (127.0.0.1).
1757
1758instaweb.modulePath::
1759        The default module path for linkgit:git-instaweb[1] to use
1760        instead of /usr/lib/apache2/modules.  Only used if httpd
1761        is Apache.
1762
1763instaweb.port::
1764        The port number to bind the gitweb httpd to. See
1765        linkgit:git-instaweb[1].
1766
1767interactive.singleKey::
1768        In interactive commands, allow the user to provide one-letter
1769        input with a single key (i.e., without hitting enter).
1770        Currently this is used by the `--patch` mode of
1771        linkgit:git-add[1], linkgit:git-checkout[1], linkgit:git-commit[1],
1772        linkgit:git-reset[1], and linkgit:git-stash[1]. Note that this
1773        setting is silently ignored if portable keystroke input
1774        is not available; requires the Perl module Term::ReadKey.
1775
1776log.abbrevCommit::
1777        If true, makes linkgit:git-log[1], linkgit:git-show[1], and
1778        linkgit:git-whatchanged[1] assume `--abbrev-commit`. You may
1779        override this option with `--no-abbrev-commit`.
1780
1781log.date::
1782        Set the default date-time mode for the 'log' command.
1783        Setting a value for log.date is similar to using 'git log''s
1784        `--date` option.  Possible values are `relative`, `local`,
1785        `default`, `iso`, `rfc`, and `short`; see linkgit:git-log[1]
1786        for details.
1787
1788log.decorate::
1789        Print out the ref names of any commits that are shown by the log
1790        command. If 'short' is specified, the ref name prefixes 'refs/heads/',
1791        'refs/tags/' and 'refs/remotes/' will not be printed. If 'full' is
1792        specified, the full ref name (including prefix) will be printed.
1793        This is the same as the log commands '--decorate' option.
1794
1795log.showRoot::
1796        If true, the initial commit will be shown as a big creation event.
1797        This is equivalent to a diff against an empty tree.
1798        Tools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which
1799        normally hide the root commit will now show it. True by default.
1800
1801log.mailmap::
1802        If true, makes linkgit:git-log[1], linkgit:git-show[1], and
1803        linkgit:git-whatchanged[1] assume `--use-mailmap`.
1804
1805mailinfo.scissors::
1806        If true, makes linkgit:git-mailinfo[1] (and therefore
1807        linkgit:git-am[1]) act by default as if the --scissors option
1808        was provided on the command-line. When active, this features
1809        removes everything from the message body before a scissors
1810        line (i.e. consisting mainly of ">8", "8<" and "-").
1811
1812mailmap.file::
1813        The location of an augmenting mailmap file. The default
1814        mailmap, located in the root of the repository, is loaded
1815        first, then the mailmap file pointed to by this variable.
1816        The location of the mailmap file may be in a repository
1817        subdirectory, or somewhere outside of the repository itself.
1818        See linkgit:git-shortlog[1] and linkgit:git-blame[1].
1819
1820mailmap.blob::
1821        Like `mailmap.file`, but consider the value as a reference to a
1822        blob in the repository. If both `mailmap.file` and
1823        `mailmap.blob` are given, both are parsed, with entries from
1824        `mailmap.file` taking precedence. In a bare repository, this
1825        defaults to `HEAD:.mailmap`. In a non-bare repository, it
1826        defaults to empty.
1827
1828man.viewer::
1829        Specify the programs that may be used to display help in the
1830        'man' format. See linkgit:git-help[1].
1831
1832man.<tool>.cmd::
1833        Specify the command to invoke the specified man viewer. The
1834        specified command is evaluated in shell with the man page
1835        passed as argument. (See linkgit:git-help[1].)
1836
1837man.<tool>.path::
1838        Override the path for the given tool that may be used to
1839        display help in the 'man' format. See linkgit:git-help[1].
1840
1841include::merge-config.txt[]
1842
1843mergetool.<tool>.path::
1844        Override the path for the given tool.  This is useful in case
1845        your tool is not in the PATH.
1846
1847mergetool.<tool>.cmd::
1848        Specify the command to invoke the specified merge tool.  The
1849        specified command is evaluated in shell with the following
1850        variables available: 'BASE' is the name of a temporary file
1851        containing the common base of the files to be merged, if available;
1852        'LOCAL' is the name of a temporary file containing the contents of
1853        the file on the current branch; 'REMOTE' is the name of a temporary
1854        file containing the contents of the file from the branch being
1855        merged; 'MERGED' contains the name of the file to which the merge
1856        tool should write the results of a successful merge.
1857
1858mergetool.<tool>.trustExitCode::
1859        For a custom merge command, specify whether the exit code of
1860        the merge command can be used to determine whether the merge was
1861        successful.  If this is not set to true then the merge target file
1862        timestamp is checked and the merge assumed to have been successful
1863        if the file has been updated, otherwise the user is prompted to
1864        indicate the success of the merge.
1865
1866mergetool.meld.hasOutput::
1867        Older versions of `meld` do not support the `--output` option.
1868        Git will attempt to detect whether `meld` supports `--output`
1869        by inspecting the output of `meld --help`.  Configuring
1870        `mergetool.meld.hasOutput` will make Git skip these checks and
1871        use the configured value instead.  Setting `mergetool.meld.hasOutput`
1872        to `true` tells Git to unconditionally use the `--output` option,
1873        and `false` avoids using `--output`.
1874
1875mergetool.keepBackup::
1876        After performing a merge, the original file with conflict markers
1877        can be saved as a file with a `.orig` extension.  If this variable
1878        is set to `false` then this file is not preserved.  Defaults to
1879        `true` (i.e. keep the backup files).
1880
1881mergetool.keepTemporaries::
1882        When invoking a custom merge tool, Git uses a set of temporary
1883        files to pass to the tool. If the tool returns an error and this
1884        variable is set to `true`, then these temporary files will be
1885        preserved, otherwise they will be removed after the tool has
1886        exited. Defaults to `false`.
1887
1888mergetool.writeToTemp::
1889        Git writes temporary 'BASE', 'LOCAL', and 'REMOTE' versions of
1890        conflicting files in the worktree by default.  Git will attempt
1891        to use a temporary directory for these files when set `true`.
1892        Defaults to `false`.
1893
1894mergetool.prompt::
1895        Prompt before each invocation of the merge resolution program.
1896
1897notes.displayRef::
1898        The (fully qualified) refname from which to show notes when
1899        showing commit messages.  The value of this variable can be set
1900        to a glob, in which case notes from all matching refs will be
1901        shown.  You may also specify this configuration variable
1902        several times.  A warning will be issued for refs that do not
1903        exist, but a glob that does not match any refs is silently
1904        ignored.
1905+
1906This setting can be overridden with the `GIT_NOTES_DISPLAY_REF`
1907environment variable, which must be a colon separated list of refs or
1908globs.
1909+
1910The effective value of "core.notesRef" (possibly overridden by
1911GIT_NOTES_REF) is also implicitly added to the list of refs to be
1912displayed.
1913
1914notes.rewrite.<command>::
1915        When rewriting commits with <command> (currently `amend` or
1916        `rebase`) and this variable is set to `true`, Git
1917        automatically copies your notes from the original to the
1918        rewritten commit.  Defaults to `true`, but see
1919        "notes.rewriteRef" below.
1920
1921notes.rewriteMode::
1922        When copying notes during a rewrite (see the
1923        "notes.rewrite.<command>" option), determines what to do if
1924        the target commit already has a note.  Must be one of
1925        `overwrite`, `concatenate`, or `ignore`.  Defaults to
1926        `concatenate`.
1927+
1928This setting can be overridden with the `GIT_NOTES_REWRITE_MODE`
1929environment variable.
1930
1931notes.rewriteRef::
1932        When copying notes during a rewrite, specifies the (fully
1933        qualified) ref whose notes should be copied.  The ref may be a
1934        glob, in which case notes in all matching refs will be copied.
1935        You may also specify this configuration several times.
1936+
1937Does not have a default value; you must configure this variable to
1938enable note rewriting.  Set it to `refs/notes/commits` to enable
1939rewriting for the default commit notes.
1940+
1941This setting can be overridden with the `GIT_NOTES_REWRITE_REF`
1942environment variable, which must be a colon separated list of refs or
1943globs.
1944
1945pack.window::
1946        The size of the window used by linkgit:git-pack-objects[1] when no
1947        window size is given on the command line. Defaults to 10.
1948
1949pack.depth::
1950        The maximum delta depth used by linkgit:git-pack-objects[1] when no
1951        maximum depth is given on the command line. Defaults to 50.
1952
1953pack.windowMemory::
1954        The maximum size of memory that is consumed by each thread
1955        in linkgit:git-pack-objects[1] for pack window memory when
1956        no limit is given on the command line.  The value can be
1957        suffixed with "k", "m", or "g".  When left unconfigured (or
1958        set explicitly to 0), there will be no limit.
1959
1960pack.compression::
1961        An integer -1..9, indicating the compression level for objects
1962        in a pack file. -1 is the zlib default. 0 means no
1963        compression, and 1..9 are various speed/size tradeoffs, 9 being
1964        slowest.  If not set,  defaults to core.compression.  If that is
1965        not set,  defaults to -1, the zlib default, which is "a default
1966        compromise between speed and compression (currently equivalent
1967        to level 6)."
1968+
1969Note that changing the compression level will not automatically recompress
1970all existing objects. You can force recompression by passing the -F option
1971to linkgit:git-repack[1].
1972
1973pack.deltaCacheSize::
1974        The maximum memory in bytes used for caching deltas in
1975        linkgit:git-pack-objects[1] before writing them out to a pack.
1976        This cache is used to speed up the writing object phase by not
1977        having to recompute the final delta result once the best match
1978        for all objects is found.  Repacking large repositories on machines
1979        which are tight with memory might be badly impacted by this though,
1980        especially if this cache pushes the system into swapping.
1981        A value of 0 means no limit. The smallest size of 1 byte may be
1982        used to virtually disable this cache. Defaults to 256 MiB.
1983
1984pack.deltaCacheLimit::
1985        The maximum size of a delta, that is cached in
1986        linkgit:git-pack-objects[1]. This cache is used to speed up the
1987        writing object phase by not having to recompute the final delta
1988        result once the best match for all objects is found. Defaults to 1000.
1989
1990pack.threads::
1991        Specifies the number of threads to spawn when searching for best
1992        delta matches.  This requires that linkgit:git-pack-objects[1]
1993        be compiled with pthreads otherwise this option is ignored with a
1994        warning. This is meant to reduce packing time on multiprocessor
1995        machines. The required amount of memory for the delta search window
1996        is however multiplied by the number of threads.
1997        Specifying 0 will cause Git to auto-detect the number of CPU's
1998        and set the number of threads accordingly.
1999
2000pack.indexVersion::
2001        Specify the default pack index version.  Valid values are 1 for
2002        legacy pack index used by Git versions prior to 1.5.2, and 2 for
2003        the new pack index with capabilities for packs larger than 4 GB
2004        as well as proper protection against the repacking of corrupted
2005        packs.  Version 2 is the default.  Note that version 2 is enforced
2006        and this config option ignored whenever the corresponding pack is
2007        larger than 2 GB.
2008+
2009If you have an old Git that does not understand the version 2 `*.idx` file,
2010cloning or fetching over a non native protocol (e.g. "http" and "rsync")
2011that will copy both `*.pack` file and corresponding `*.idx` file from the
2012other side may give you a repository that cannot be accessed with your
2013older version of Git. If the `*.pack` file is smaller than 2 GB, however,
2014you can use linkgit:git-index-pack[1] on the *.pack file to regenerate
2015the `*.idx` file.
2016
2017pack.packSizeLimit::
2018        The maximum size of a pack.  This setting only affects
2019        packing to a file when repacking, i.e. the git:// protocol
2020        is unaffected.  It can be overridden by the `--max-pack-size`
2021        option of linkgit:git-repack[1]. The minimum size allowed is
2022        limited to 1 MiB. The default is unlimited.
2023        Common unit suffixes of 'k', 'm', or 'g' are
2024        supported.
2025
2026pack.useBitmaps::
2027        When true, git will use pack bitmaps (if available) when packing
2028        to stdout (e.g., during the server side of a fetch). Defaults to
2029        true. You should not generally need to turn this off unless
2030        you are debugging pack bitmaps.
2031
2032pack.writeBitmaps (deprecated)::
2033        This is a deprecated synonym for `repack.writeBitmaps`.
2034
2035pack.writeBitmapHashCache::
2036        When true, git will include a "hash cache" section in the bitmap
2037        index (if one is written). This cache can be used to feed git's
2038        delta heuristics, potentially leading to better deltas between
2039        bitmapped and non-bitmapped objects (e.g., when serving a fetch
2040        between an older, bitmapped pack and objects that have been
2041        pushed since the last gc). The downside is that it consumes 4
2042        bytes per object of disk space, and that JGit's bitmap
2043        implementation does not understand it, causing it to complain if
2044        Git and JGit are used on the same repository. Defaults to false.
2045
2046pager.<cmd>::
2047        If the value is boolean, turns on or off pagination of the
2048        output of a particular Git subcommand when writing to a tty.
2049        Otherwise, turns on pagination for the subcommand using the
2050        pager specified by the value of `pager.<cmd>`.  If `--paginate`
2051        or `--no-pager` is specified on the command line, it takes
2052        precedence over this option.  To disable pagination for all
2053        commands, set `core.pager` or `GIT_PAGER` to `cat`.
2054
2055pretty.<name>::
2056        Alias for a --pretty= format string, as specified in
2057        linkgit:git-log[1]. Any aliases defined here can be used just
2058        as the built-in pretty formats could. For example,
2059        running `git config pretty.changelog "format:* %H %s"`
2060        would cause the invocation `git log --pretty=changelog`
2061        to be equivalent to running `git log "--pretty=format:* %H %s"`.
2062        Note that an alias with the same name as a built-in format
2063        will be silently ignored.
2064
2065pull.ff::
2066        By default, Git does not create an extra merge commit when merging
2067        a commit that is a descendant of the current commit. Instead, the
2068        tip of the current branch is fast-forwarded. When set to `false`,
2069        this variable tells Git to create an extra merge commit in such
2070        a case (equivalent to giving the `--no-ff` option from the command
2071        line). When set to `only`, only such fast-forward merges are
2072        allowed (equivalent to giving the `--ff-only` option from the
2073        command line). This setting overrides `merge.ff` when pulling.
2074
2075pull.rebase::
2076        When true, rebase branches on top of the fetched branch, instead
2077        of merging the default branch from the default remote when "git
2078        pull" is run. See "branch.<name>.rebase" for setting this on a
2079        per-branch basis.
2080+
2081        When preserve, also pass `--preserve-merges` along to 'git rebase'
2082        so that locally committed merge commits will not be flattened
2083        by running 'git pull'.
2084+
2085*NOTE*: this is a possibly dangerous operation; do *not* use
2086it unless you understand the implications (see linkgit:git-rebase[1]
2087for details).
2088
2089pull.octopus::
2090        The default merge strategy to use when pulling multiple branches
2091        at once.
2092
2093pull.twohead::
2094        The default merge strategy to use when pulling a single branch.
2095
2096push.default::
2097        Defines the action `git push` should take if no refspec is
2098        explicitly given.  Different values are well-suited for
2099        specific workflows; for instance, in a purely central workflow
2100        (i.e. the fetch source is equal to the push destination),
2101        `upstream` is probably what you want.  Possible values are:
2102+
2103--
2104
2105* `nothing` - do not push anything (error out) unless a refspec is
2106  explicitly given. This is primarily meant for people who want to
2107  avoid mistakes by always being explicit.
2108
2109* `current` - push the current branch to update a branch with the same
2110  name on the receiving end.  Works in both central and non-central
2111  workflows.
2112
2113* `upstream` - push the current branch back to the branch whose
2114  changes are usually integrated into the current branch (which is
2115  called `@{upstream}`).  This mode only makes sense if you are
2116  pushing to the same repository you would normally pull from
2117  (i.e. central workflow).
2118
2119* `simple` - in centralized workflow, work like `upstream` with an
2120  added safety to refuse to push if the upstream branch's name is
2121  different from the local one.
2122+
2123When pushing to a remote that is different from the remote you normally
2124pull from, work as `current`.  This is the safest option and is suited
2125for beginners.
2126+
2127This mode has become the default in Git 2.0.
2128
2129* `matching` - push all branches having the same name on both ends.
2130  This makes the repository you are pushing to remember the set of
2131  branches that will be pushed out (e.g. if you always push 'maint'
2132  and 'master' there and no other branches, the repository you push
2133  to will have these two branches, and your local 'maint' and
2134  'master' will be pushed there).
2135+
2136To use this mode effectively, you have to make sure _all_ the
2137branches you would push out are ready to be pushed out before
2138running 'git push', as the whole point of this mode is to allow you
2139to push all of the branches in one go.  If you usually finish work
2140on only one branch and push out the result, while other branches are
2141unfinished, this mode is not for you.  Also this mode is not
2142suitable for pushing into a shared central repository, as other
2143people may add new branches there, or update the tip of existing
2144branches outside your control.
2145+
2146This used to be the default, but not since Git 2.0 (`simple` is the
2147new default).
2148
2149--
2150
2151push.followTags::
2152        If set to true enable '--follow-tags' option by default.  You
2153        may override this configuration at time of push by specifying
2154        '--no-follow-tags'.
2155
2156
2157rebase.stat::
2158        Whether to show a diffstat of what changed upstream since the last
2159        rebase. False by default.
2160
2161rebase.autoSquash::
2162        If set to true enable '--autosquash' option by default.
2163
2164rebase.autoStash::
2165        When set to true, automatically create a temporary stash
2166        before the operation begins, and apply it after the operation
2167        ends.  This means that you can run rebase on a dirty worktree.
2168        However, use with care: the final stash application after a
2169        successful rebase might result in non-trivial conflicts.
2170        Defaults to false.
2171
2172receive.advertiseAtomic::
2173        By default, git-receive-pack will advertise the atomic push
2174        capability to its clients. If you don't want to this capability
2175        to be advertised, set this variable to false.
2176
2177receive.autogc::
2178        By default, git-receive-pack will run "git-gc --auto" after
2179        receiving data from git-push and updating refs.  You can stop
2180        it by setting this variable to false.
2181
2182receive.certNonceSeed::
2183        By setting this variable to a string, `git receive-pack`
2184        will accept a `git push --signed` and verifies it by using
2185        a "nonce" protected by HMAC using this string as a secret
2186        key.
2187
2188receive.certNonceSlop::
2189        When a `git push --signed` sent a push certificate with a
2190        "nonce" that was issued by a receive-pack serving the same
2191        repository within this many seconds, export the "nonce"
2192        found in the certificate to `GIT_PUSH_CERT_NONCE` to the
2193        hooks (instead of what the receive-pack asked the sending
2194        side to include).  This may allow writing checks in
2195        `pre-receive` and `post-receive` a bit easier.  Instead of
2196        checking `GIT_PUSH_CERT_NONCE_SLOP` environment variable
2197        that records by how many seconds the nonce is stale to
2198        decide if they want to accept the certificate, they only
2199        can check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.
2200
2201receive.fsckObjects::
2202        If it is set to true, git-receive-pack will check all received
2203        objects. It will abort in the case of a malformed object or a
2204        broken link. The result of an abort are only dangling objects.
2205        Defaults to false. If not set, the value of `transfer.fsckObjects`
2206        is used instead.
2207
2208receive.unpackLimit::
2209        If the number of objects received in a push is below this
2210        limit then the objects will be unpacked into loose object
2211        files. However if the number of received objects equals or
2212        exceeds this limit then the received pack will be stored as
2213        a pack, after adding any missing delta bases.  Storing the
2214        pack from a push can make the push operation complete faster,
2215        especially on slow filesystems.  If not set, the value of
2216        `transfer.unpackLimit` is used instead.
2217
2218receive.denyDeletes::
2219        If set to true, git-receive-pack will deny a ref update that deletes
2220        the ref. Use this to prevent such a ref deletion via a push.
2221
2222receive.denyDeleteCurrent::
2223        If set to true, git-receive-pack will deny a ref update that
2224        deletes the currently checked out branch of a non-bare repository.
2225
2226receive.denyCurrentBranch::
2227        If set to true or "refuse", git-receive-pack will deny a ref update
2228        to the currently checked out branch of a non-bare repository.
2229        Such a push is potentially dangerous because it brings the HEAD
2230        out of sync with the index and working tree. If set to "warn",
2231        print a warning of such a push to stderr, but allow the push to
2232        proceed. If set to false or "ignore", allow such pushes with no
2233        message. Defaults to "refuse".
2234+
2235Another option is "updateInstead" which will update the working
2236tree if pushing into the current branch.  This option is
2237intended for synchronizing working directories when one side is not easily
2238accessible via interactive ssh (e.g. a live web site, hence the requirement
2239that the working directory be clean). This mode also comes in handy when
2240developing inside a VM to test and fix code on different Operating Systems.
2241+
2242By default, "updateInstead" will refuse the push if the working tree or
2243the index have any difference from the HEAD, but the `push-to-checkout`
2244hook can be used to customize this.  See linkgit:githooks[5].
2245
2246receive.denyNonFastForwards::
2247        If set to true, git-receive-pack will deny a ref update which is
2248        not a fast-forward. Use this to prevent such an update via a push,
2249        even if that push is forced. This configuration variable is
2250        set when initializing a shared repository.
2251
2252receive.hideRefs::
2253        String(s) `receive-pack` uses to decide which refs to omit
2254        from its initial advertisement.  Use more than one
2255        definitions to specify multiple prefix strings. A ref that
2256        are under the hierarchies listed on the value of this
2257        variable is excluded, and is hidden when responding to `git
2258        push`, and an attempt to update or delete a hidden ref by
2259        `git push` is rejected.
2260
2261receive.updateServerInfo::
2262        If set to true, git-receive-pack will run git-update-server-info
2263        after receiving data from git-push and updating refs.
2264
2265receive.shallowUpdate::
2266        If set to true, .git/shallow can be updated when new refs
2267        require new shallow roots. Otherwise those refs are rejected.
2268
2269remote.pushDefault::
2270        The remote to push to by default.  Overrides
2271        `branch.<name>.remote` for all branches, and is overridden by
2272        `branch.<name>.pushRemote` for specific branches.
2273
2274remote.<name>.url::
2275        The URL of a remote repository.  See linkgit:git-fetch[1] or
2276        linkgit:git-push[1].
2277
2278remote.<name>.pushurl::
2279        The push URL of a remote repository.  See linkgit:git-push[1].
2280
2281remote.<name>.proxy::
2282        For remotes that require curl (http, https and ftp), the URL to
2283        the proxy to use for that remote.  Set to the empty string to
2284        disable proxying for that remote.
2285
2286remote.<name>.fetch::
2287        The default set of "refspec" for linkgit:git-fetch[1]. See
2288        linkgit:git-fetch[1].
2289
2290remote.<name>.push::
2291        The default set of "refspec" for linkgit:git-push[1]. See
2292        linkgit:git-push[1].
2293
2294remote.<name>.mirror::
2295        If true, pushing to this remote will automatically behave
2296        as if the `--mirror` option was given on the command line.
2297
2298remote.<name>.skipDefaultUpdate::
2299        If true, this remote will be skipped by default when updating
2300        using linkgit:git-fetch[1] or the `update` subcommand of
2301        linkgit:git-remote[1].
2302
2303remote.<name>.skipFetchAll::
2304        If true, this remote will be skipped by default when updating
2305        using linkgit:git-fetch[1] or the `update` subcommand of
2306        linkgit:git-remote[1].
2307
2308remote.<name>.receivepack::
2309        The default program to execute on the remote side when pushing.  See
2310        option --receive-pack of linkgit:git-push[1].
2311
2312remote.<name>.uploadpack::
2313        The default program to execute on the remote side when fetching.  See
2314        option --upload-pack of linkgit:git-fetch-pack[1].
2315
2316remote.<name>.tagOpt::
2317        Setting this value to --no-tags disables automatic tag following when
2318        fetching from remote <name>. Setting it to --tags will fetch every
2319        tag from remote <name>, even if they are not reachable from remote
2320        branch heads. Passing these flags directly to linkgit:git-fetch[1] can
2321        override this setting. See options --tags and --no-tags of
2322        linkgit:git-fetch[1].
2323
2324remote.<name>.vcs::
2325        Setting this to a value <vcs> will cause Git to interact with
2326        the remote with the git-remote-<vcs> helper.
2327
2328remote.<name>.prune::
2329        When set to true, fetching from this remote by default will also
2330        remove any remote-tracking references that no longer exist on the
2331        remote (as if the `--prune` option was given on the command line).
2332        Overrides `fetch.prune` settings, if any.
2333
2334remotes.<group>::
2335        The list of remotes which are fetched by "git remote update
2336        <group>".  See linkgit:git-remote[1].
2337
2338repack.useDeltaBaseOffset::
2339        By default, linkgit:git-repack[1] creates packs that use
2340        delta-base offset. If you need to share your repository with
2341        Git older than version 1.4.4, either directly or via a dumb
2342        protocol such as http, then you need to set this option to
2343        "false" and repack. Access from old Git versions over the
2344        native protocol are unaffected by this option.
2345
2346repack.packKeptObjects::
2347        If set to true, makes `git repack` act as if
2348        `--pack-kept-objects` was passed. See linkgit:git-repack[1] for
2349        details. Defaults to `false` normally, but `true` if a bitmap
2350        index is being written (either via `--write-bitmap-index` or
2351        `repack.writeBitmaps`).
2352
2353repack.writeBitmaps::
2354        When true, git will write a bitmap index when packing all
2355        objects to disk (e.g., when `git repack -a` is run).  This
2356        index can speed up the "counting objects" phase of subsequent
2357        packs created for clones and fetches, at the cost of some disk
2358        space and extra time spent on the initial repack.  Defaults to
2359        false.
2360
2361rerere.autoUpdate::
2362        When set to true, `git-rerere` updates the index with the
2363        resulting contents after it cleanly resolves conflicts using
2364        previously recorded resolution.  Defaults to false.
2365
2366rerere.enabled::
2367        Activate recording of resolved conflicts, so that identical
2368        conflict hunks can be resolved automatically, should they be
2369        encountered again.  By default, linkgit:git-rerere[1] is
2370        enabled if there is an `rr-cache` directory under the
2371        `$GIT_DIR`, e.g. if "rerere" was previously used in the
2372        repository.
2373
2374sendemail.identity::
2375        A configuration identity. When given, causes values in the
2376        'sendemail.<identity>' subsection to take precedence over
2377        values in the 'sendemail' section. The default identity is
2378        the value of 'sendemail.identity'.
2379
2380sendemail.smtpEncryption::
2381        See linkgit:git-send-email[1] for description.  Note that this
2382        setting is not subject to the 'identity' mechanism.
2383
2384sendemail.smtpssl (deprecated)::
2385        Deprecated alias for 'sendemail.smtpEncryption = ssl'.
2386
2387sendemail.smtpsslcertpath::
2388        Path to ca-certificates (either a directory or a single file).
2389        Set it to an empty string to disable certificate verification.
2390
2391sendemail.<identity>.*::
2392        Identity-specific versions of the 'sendemail.*' parameters
2393        found below, taking precedence over those when the this
2394        identity is selected, through command-line or
2395        'sendemail.identity'.
2396
2397sendemail.aliasesFile::
2398sendemail.aliasFileType::
2399sendemail.annotate::
2400sendemail.bcc::
2401sendemail.cc::
2402sendemail.ccCmd::
2403sendemail.chainReplyTo::
2404sendemail.confirm::
2405sendemail.envelopeSender::
2406sendemail.from::
2407sendemail.multiEdit::
2408sendemail.signedoffbycc::
2409sendemail.smtpPass::
2410sendemail.suppresscc::
2411sendemail.suppressFrom::
2412sendemail.to::
2413sendemail.smtpDomain::
2414sendemail.smtpServer::
2415sendemail.smtpServerPort::
2416sendemail.smtpServerOption::
2417sendemail.smtpUser::
2418sendemail.thread::
2419sendemail.transferEncoding::
2420sendemail.validate::
2421sendemail.xmailer::
2422        See linkgit:git-send-email[1] for description.
2423
2424sendemail.signedoffcc (deprecated)::
2425        Deprecated alias for 'sendemail.signedoffbycc'.
2426
2427showbranch.default::
2428        The default set of branches for linkgit:git-show-branch[1].
2429        See linkgit:git-show-branch[1].
2430
2431status.relativePaths::
2432        By default, linkgit:git-status[1] shows paths relative to the
2433        current directory. Setting this variable to `false` shows paths
2434        relative to the repository root (this was the default for Git
2435        prior to v1.5.4).
2436
2437status.short::
2438        Set to true to enable --short by default in linkgit:git-status[1].
2439        The option --no-short takes precedence over this variable.
2440
2441status.branch::
2442        Set to true to enable --branch by default in linkgit:git-status[1].
2443        The option --no-branch takes precedence over this variable.
2444
2445status.displayCommentPrefix::
2446        If set to true, linkgit:git-status[1] will insert a comment
2447        prefix before each output line (starting with
2448        `core.commentChar`, i.e. `#` by default). This was the
2449        behavior of linkgit:git-status[1] in Git 1.8.4 and previous.
2450        Defaults to false.
2451
2452status.showUntrackedFiles::
2453        By default, linkgit:git-status[1] and linkgit:git-commit[1] show
2454        files which are not currently tracked by Git. Directories which
2455        contain only untracked files, are shown with the directory name
2456        only. Showing untracked files means that Git needs to lstat() all
2457        the files in the whole repository, which might be slow on some
2458        systems. So, this variable controls how the commands displays
2459        the untracked files. Possible values are:
2460+
2461--
2462* `no` - Show no untracked files.
2463* `normal` - Show untracked files and directories.
2464* `all` - Show also individual files in untracked directories.
2465--
2466+
2467If this variable is not specified, it defaults to 'normal'.
2468This variable can be overridden with the -u|--untracked-files option
2469of linkgit:git-status[1] and linkgit:git-commit[1].
2470
2471status.submoduleSummary::
2472        Defaults to false.
2473        If this is set to a non zero number or true (identical to -1 or an
2474        unlimited number), the submodule summary will be enabled and a
2475        summary of commits for modified submodules will be shown (see
2476        --summary-limit option of linkgit:git-submodule[1]). Please note
2477        that the summary output command will be suppressed for all
2478        submodules when `diff.ignoreSubmodules` is set to 'all' or only
2479        for those submodules where `submodule.<name>.ignore=all`. The only
2480        exception to that rule is that status and commit will show staged
2481        submodule changes. To
2482        also view the summary for ignored submodules you can either use
2483        the --ignore-submodules=dirty command-line option or the 'git
2484        submodule summary' command, which shows a similar output but does
2485        not honor these settings.
2486
2487submodule.<name>.path::
2488submodule.<name>.url::
2489        The path within this project and URL for a submodule. These
2490        variables are initially populated by 'git submodule init'. See
2491        linkgit:git-submodule[1] and linkgit:gitmodules[5] for
2492        details.
2493
2494submodule.<name>.update::
2495        The default update procedure for a submodule. This variable
2496        is populated by `git submodule init` from the
2497        linkgit:gitmodules[5] file. See description of 'update'
2498        command in linkgit:git-submodule[1].
2499
2500submodule.<name>.branch::
2501        The remote branch name for a submodule, used by `git submodule
2502        update --remote`.  Set this option to override the value found in
2503        the `.gitmodules` file.  See linkgit:git-submodule[1] and
2504        linkgit:gitmodules[5] for details.
2505
2506submodule.<name>.fetchRecurseSubmodules::
2507        This option can be used to control recursive fetching of this
2508        submodule. It can be overridden by using the --[no-]recurse-submodules
2509        command-line option to "git fetch" and "git pull".
2510        This setting will override that from in the linkgit:gitmodules[5]
2511        file.
2512
2513submodule.<name>.ignore::
2514        Defines under what circumstances "git status" and the diff family show
2515        a submodule as modified. When set to "all", it will never be considered
2516        modified (but it will nonetheless show up in the output of status and
2517        commit when it has been staged), "dirty" will ignore all changes
2518        to the submodules work tree and
2519        takes only differences between the HEAD of the submodule and the commit
2520        recorded in the superproject into account. "untracked" will additionally
2521        let submodules with modified tracked files in their work tree show up.
2522        Using "none" (the default when this option is not set) also shows
2523        submodules that have untracked files in their work tree as changed.
2524        This setting overrides any setting made in .gitmodules for this submodule,
2525        both settings can be overridden on the command line by using the
2526        "--ignore-submodules" option. The 'git submodule' commands are not
2527        affected by this setting.
2528
2529tag.sort::
2530        This variable controls the sort ordering of tags when displayed by
2531        linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the
2532        value of this variable will be used as the default.
2533
2534tar.umask::
2535        This variable can be used to restrict the permission bits of
2536        tar archive entries.  The default is 0002, which turns off the
2537        world write bit.  The special value "user" indicates that the
2538        archiving user's umask will be used instead.  See umask(2) and
2539        linkgit:git-archive[1].
2540
2541transfer.fsckObjects::
2542        When `fetch.fsckObjects` or `receive.fsckObjects` are
2543        not set, the value of this variable is used instead.
2544        Defaults to false.
2545
2546transfer.hideRefs::
2547        This variable can be used to set both `receive.hideRefs`
2548        and `uploadpack.hideRefs` at the same time to the same
2549        values.  See entries for these other variables.
2550
2551transfer.unpackLimit::
2552        When `fetch.unpackLimit` or `receive.unpackLimit` are
2553        not set, the value of this variable is used instead.
2554        The default value is 100.
2555
2556uploadarchive.allowUnreachable::
2557        If true, allow clients to use `git archive --remote` to request
2558        any tree, whether reachable from the ref tips or not. See the
2559        discussion in the `SECURITY` section of
2560        linkgit:git-upload-archive[1] for more details. Defaults to
2561        `false`.
2562
2563uploadpack.hideRefs::
2564        String(s) `upload-pack` uses to decide which refs to omit
2565        from its initial advertisement.  Use more than one
2566        definitions to specify multiple prefix strings. A ref that
2567        are under the hierarchies listed on the value of this
2568        variable is excluded, and is hidden from `git ls-remote`,
2569        `git fetch`, etc.  An attempt to fetch a hidden ref by `git
2570        fetch` will fail.  See also `uploadpack.allowTipSHA1InWant`.
2571
2572uploadpack.allowTipSHA1InWant::
2573        When `uploadpack.hideRefs` is in effect, allow `upload-pack`
2574        to accept a fetch request that asks for an object at the tip
2575        of a hidden ref (by default, such a request is rejected).
2576        see also `uploadpack.hideRefs`.
2577
2578uploadpack.allowReachableSHA1InWant::
2579        Allow `upload-pack` to accept a fetch request that asks for an
2580        object that is reachable from any ref tip. However, note that
2581        calculating object reachability is computationally expensive.
2582        Defaults to `false`.
2583
2584uploadpack.keepAlive::
2585        When `upload-pack` has started `pack-objects`, there may be a
2586        quiet period while `pack-objects` prepares the pack. Normally
2587        it would output progress information, but if `--quiet` was used
2588        for the fetch, `pack-objects` will output nothing at all until
2589        the pack data begins. Some clients and networks may consider
2590        the server to be hung and give up. Setting this option instructs
2591        `upload-pack` to send an empty keepalive packet every
2592        `uploadpack.keepAlive` seconds. Setting this option to 0
2593        disables keepalive packets entirely. The default is 5 seconds.
2594
2595url.<base>.insteadOf::
2596        Any URL that starts with this value will be rewritten to
2597        start, instead, with <base>. In cases where some site serves a
2598        large number of repositories, and serves them with multiple
2599        access methods, and some users need to use different access
2600        methods, this feature allows people to specify any of the
2601        equivalent URLs and have Git automatically rewrite the URL to
2602        the best alternative for the particular user, even for a
2603        never-before-seen repository on the site.  When more than one
2604        insteadOf strings match a given URL, the longest match is used.
2605
2606url.<base>.pushInsteadOf::
2607        Any URL that starts with this value will not be pushed to;
2608        instead, it will be rewritten to start with <base>, and the
2609        resulting URL will be pushed to. In cases where some site serves
2610        a large number of repositories, and serves them with multiple
2611        access methods, some of which do not allow push, this feature
2612        allows people to specify a pull-only URL and have Git
2613        automatically use an appropriate URL to push, even for a
2614        never-before-seen repository on the site.  When more than one
2615        pushInsteadOf strings match a given URL, the longest match is
2616        used.  If a remote has an explicit pushurl, Git will ignore this
2617        setting for that remote.
2618
2619user.email::
2620        Your email address to be recorded in any newly created commits.
2621        Can be overridden by the 'GIT_AUTHOR_EMAIL', 'GIT_COMMITTER_EMAIL', and
2622        'EMAIL' environment variables.  See linkgit:git-commit-tree[1].
2623
2624user.name::
2625        Your full name to be recorded in any newly created commits.
2626        Can be overridden by the 'GIT_AUTHOR_NAME' and 'GIT_COMMITTER_NAME'
2627        environment variables.  See linkgit:git-commit-tree[1].
2628
2629user.signingKey::
2630        If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the
2631        key you want it to automatically when creating a signed tag or
2632        commit, you can override the default selection with this variable.
2633        This option is passed unchanged to gpg's --local-user parameter,
2634        so you may specify a key using any method that gpg supports.
2635
2636versionsort.prereleaseSuffix::
2637        When version sort is used in linkgit:git-tag[1], prerelease
2638        tags (e.g. "1.0-rc1") may appear after the main release
2639        "1.0". By specifying the suffix "-rc" in this variable,
2640        "1.0-rc1" will appear before "1.0".
2641+
2642This variable can be specified multiple times, once per suffix. The
2643order of suffixes in the config file determines the sorting order
2644(e.g. if "-pre" appears before "-rc" in the config file then 1.0-preXX
2645is sorted before 1.0-rcXX). The sorting order between different
2646suffixes is undefined if they are in multiple config files.
2647
2648web.browser::
2649        Specify a web browser that may be used by some commands.
2650        Currently only linkgit:git-instaweb[1] and linkgit:git-help[1]
2651        may use it.